GitHub Issue Workflow
SkillDev toolsFetch GitHub issue, create branch, plan and implement with TDD, then open PR
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the GitHub Issue Workflow skill
What this skill tells your AI
The instructions your AI receives, as published by typeddevs/bashunit in .claude/skills/gh-issue/SKILL.md and read by ahel’s review.
Fetch a GitHub issue, create branch, implement following TDD, and open a PR.
Arguments
$ARGUMENTS- Issue number (e.g.,42or#42)
Instructions
Phase 1: Setup
-
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 documentation
-
Create a branch from
main:Determine prefix from labels:
bug→fix/enhancement→feat/documentation→docs/- Default →
feat/
Branch name:
<prefix><issue-number>-<slug>(slug: lowercase title, spaces →-, max 50 chars)git checkout main && git pull git checkout -b <branch-name>
Phase 2: Plan
-
Analyze the issue: requirements, labels, referenced issues, affected areas
-
Explore the codebase for context:
- Find related code in
src/ - Find related tests in
tests/ - Study existing patterns
- Find related code in
-
Create implementation plan:
- Acceptance Criteria
- Test Strategy (which tests to write first)
- Files to Change
- Implementation Order (smallest first step)
-
Use EnterPlanMode if implementation is non-trivial
Phase 3: Implement
-
Follow strict TDD workflow (see @.claude/rules/tdd-workflow.md):
For each test:
- RED - Write failing test, verify it fails for the RIGHT reason
- GREEN - Minimal code to pass
- REFACTOR - Improve while keeping tests green
-
Run full test suite frequently:
./bashunit tests/ ./bashunit --parallel tests/ -
Quality checks after each refactor:
make sa && make lint
Phase 4: Ship
-
Final verification:
./bashunit tests/ && ./bashunit --parallel tests/ && make sa && make lint -
Commit using conventional commits with
Closes #<issue-number> -
Create PR using the
/prskill:/pr #<issue-number>
Output Format
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
Signals
- GitHub stars
- 425
- Forks
- 57
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
gh-issue-typeddevs- Source
- github.com/typeddevs/bashunit