Menú
Fetch GitHub issue, create branch, plan and implement with TDD, then open PR
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Push branch and create a GitHub PR with concise, issue-linked description
Run pre-release validation and execute the release process
Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.
Add new assertion function with comprehensive tests following TDD
Analyze test coverage and identify untested code paths
Debug and fix failing tests systematically
| name | gh-issue |
| description | Fetch GitHub issue, create branch, plan and implement with TDD, then open PR |
| user-invocable | true |
| argument-hint | <issue-number> |
| allowed-tools | Bash, Read, Edit, Write, Grep, Glob, Agent, WebFetch |
Fetch a GitHub issue, create branch, implement following TDD, and open a PR.
$ARGUMENTS - Issue number (e.g., 42 or #42)Parse the issue number from $ARGUMENTS (strip # if present)
Fetch issue details:
gh issue view <number> --json title,body,labels,assignees,milestone,state
Assign yourself if unassigned:
gh issue edit <number> --add-assignee @me
Add appropriate labels if the issue doesn't have them:
bug - Something isn't workingenhancement - New feature or requestdocumentation - Improvements or additions to documentationCreate a branch from main:
Determine prefix from labels:
bug → fix/enhancement → feat/documentation → docs/feat/Branch name: <prefix><issue-number>-<slug> (slug: lowercase title, spaces → -, max 50 chars)
git checkout main && git pull
git checkout -b <branch-name>
Analyze the issue: requirements, labels, referenced issues, affected areas
Explore the codebase for context:
src/tests/Create implementation plan:
Use EnterPlanMode if implementation is non-trivial
Follow strict TDD workflow (see @.claude/rules/tdd-workflow.md):
For each test:
Run full test suite frequently:
./bashunit tests/
./bashunit --parallel tests/
Quality checks after each refactor:
make sa && make lint && shfmt -w .
Final verification:
./bashunit tests/ && ./bashunit --parallel tests/ && make sa && make lint
Commit using conventional commits with Closes #<issue-number>
Create PR using the /pr skill:
/pr #<issue-number>
After fetching, present:
## Issue #<number>: <title>
**Labels:** <labels>
**State:** <state>
**Branch:** <branch-name>
### Description
<body content>
### Next Steps
1. Explore codebase for context
2. Create implementation plan
3. Begin TDD cycle