create-issues_skill

Overview

This skill creates GitHub issues following TDD principles, Conventional Commits, and repository branch protections. It selects an appropriate issue scope, ensures labels exist, drafts a well-formed issue body with acceptance criteria and links, and documents branch/merge guidance and follow-up actions.

How this skill works

It inspects git status, current branch, open issues, and gh authentication to determine context. It applies a branch-based decision tree to decide whether to create an issue or comment on a PR, then ensures required labels exist and composes the issue using required title/body/footer structure and auto-close keywords where appropriate. Finally, it records decisions about branching strategy and next steps for the team.

When to use it

• You need a new, test-driven task aligned with repository conventions
• A PR is non-blocking and should become a future backlog item
• A change requires a multi-PR initiative (epic) and needs tracking
• A bug or regression must be captured with clear acceptance criteria
• When branch protections prevent direct pushes to main/develop

Best practices

• Always follow TDD: create the issue first, add failing tests, then implement code and PR
• Use conventional commit format for issue titles and recommend matching scopes from git history
• Keep commits atomic: one cohesive change per commit linked to the issue
• Respect protected branches: require PR + review + CI; never push directly to main/develop
• Use clear acceptance criteria and auto-closing keywords only for PR-scoped issues

Example use cases

• Create a PR-scoped issue to fix a failing API validation test and include 'Fixes #nnn' for auto-close
• Open an epic issue to coordinate a multi-PR migration (no auto-close keywords) and list linked PRs
• When on a feature branch with non-blocking feedback, create a review issue describing follow-up tasks
• On main/develop, create a priority issue directly for urgent security fixes and assign priority:high label