phel-lang/phel-pdo / .claude/skills/gh-issue
gh-issue
VerifiedFetch a GitHub issue, branch, implement with TDD, open a PR
/gh-issue
Context
!gh issue view ${ARGUMENTS#\#} --json number,url,title,body,labels,assignees,state,comments 2>/dev/null || echo "Provide an issue number"
Read the body and every comment - later comments often refine or override the original.
Steps
- Strip
#from$ARGUMENTS. Self-assign:gh issue edit <num> --add-assignee @me. - Branch from a fresh
main. Prefix by label:bug→fix/,enhancement→feat/,documentation→docs/, elsefeat/. Format:<prefix><num>-<slug>. - Plan the change: which file (
src/pdo.phelconnection-side,src/pdo/statement.phelstatement-side), whatdeftestcovers it, whether README API table + CHANGELOG need updating. Present the plan. - TDD via the
tdd-coachagent (red → green → refactor). composer test- fix everything before continuing.- Update
## [Unreleased]inCHANGELOG.md. - Commit:
<type>(<scope>): <description> Related to #<num> - Mandatory polish commit (separate
ref(...)): re-review every touched file against.claude/rules/*.md. Drop duplication, dead branches, leftover debug, naming drift, premature abstractions. If nothing surfaces, note that in the PR body. /pr #<num>.gh pr checks <pr> --watch. Fix red checks on the branch.- Merge:
gh pr merge <pr> --squash --admin --delete-branch. Fallback--auto --squash --delete-branchif--adminis rejected. Never--no-verifypast a failing required check. - Sync main:
git checkout main && git fetch origin main && git reset --hard origin/main.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |