Menu
Fetch a GitHub issue, create a branch, plan and implement with TDD, then open a PR
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add a new bashdep:: lifecycle command with TDD
Stage and commit changes using conventional commits format
Coverage gap analysis for the bashdep public API plus a bashdep::doctor audit
Debug and fix failing bashdep tests systematically
Push branch and create a GitHub PR following the bashdep PR template
Run a comprehensive pre-release validation checklist for bashdep
| name | gh-issue |
| description | Fetch a GitHub issue, create a branch, plan and implement with TDD, then open a PR |
| user-invocable | true |
| argument-hint | <issue-number> |
| allowed-tools | Bash, Read, Edit, Write, Grep, Glob, Agent, WebFetch |
Fetch a GitHub issue, create a 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
Create 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 (which bashdep:: function or doc).
Explore the codebase for context:
bashdep (single file)tests/unit/bashdep_test.shdocs/api.md or docs/behavior.mdCreate implementation plan:
bashdep, tests/unit/bashdep_test.sh,
docs/*.md, CHANGELOG.md)Use EnterPlanMode if implementation is non-trivial.
Follow strict TDD workflow (see .claude/rules/tdd-workflow.md):
For each test:
bashdep to passRun the suite frequently:
make test
Quality checks after each refactor:
make sa && make lint
Mode coverage — if the change is mutating, add tests for
BASHDEP_DRY_RUN, BASHDEP_SILENT, BASHDEP_VERBOSE,
BASHDEP_FORCE as relevant.
Final verification:
make pre_commit/run
Commit using the /commit skill, with a body referencing the
issue (e.g., 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 `bashdep` for the relevant function
2. Create implementation plan
3. Begin TDD cycle