gh-issue

GitHub Issue Workflow

Context

Read both the issue body and every comment as requirements input. Maintainer follow-ups frequently add scope, edge cases, or override the original description; when a later comment conflicts with the body, prefer the comment.

!gh issue view ${ARGUMENTS#\#} --json number,url,title,body,labels,assignees,state,comments 2>/dev/null || echo "Provide an issue number"

Instructions

Phase 1: Setup

1. Parse the issue number from $ARGUMENTS (strip # if present)

2. Assign yourself if unassigned:

   gh issue edit <number> --add-assignee @me
   

3. Create a branch from main based on the issue type:

   Determine the branch prefix from labels:

   • bug → fix/
   • enhancement → feat/
   • documentation → docs/
   • No label → feat/ (default)

   Branch name format: <prefix><issue-number>-<slug>

   git checkout main && git pull
   git checkout -b <branch-name>
   

Phase 2: Plan

1. Enter Plan Mode to design the implementation:

   • Explore the codebase to understand affected areas
   • Identify files that need changes
   • Consider the module architecture (Gacela facades, module boundaries)
   • Plan the TDD approach (what tests to write first)

2. Create implementation plan with:

   • Summary of what the issue requires
   • List of files to create/modify
   • Test strategy (unit, integration)
   • Step-by-step implementation order

Phase 3: Implement

1. After plan approval, implement following TDD:

   • Write failing tests first
   • Implement minimum code to pass
   • Refactor while keeping tests green

2. Run full test suite:

   composer test
   

   Fix ALL errors before proceeding.

Phase 4: Ship

1. Update CHANGELOG.md — add entry under ## Unreleased

2. Commit changes:

   git add <specific-files>
   git commit -m "<type>(<scope>): <description>
   
   Related to #<issue-number>"
   

3. Final refactor commit (mandatory, last commit before PR): Re-review every file touched by this change. Look for:

   • duplication introduced by the new code (extract or reuse)
   • dead branches, unused params, leftover debug
   • naming drift vs. surrounding module conventions
   • violations of .claude/rules/php.md, modules.md, compiler.md
   • over-engineering: speculative abstractions, premature interfaces