close

Close Issue $id

Follow these steps exactly, in order. Do not skip any step.

Step 1: Read the issue

Run bd show $id --json to load the title, description, acceptance criteria, parent, and labels. You need this context to write the close reason and evaluate QA.

Step 2: Quality gates (if code changed)

Check if code was modified in this session:

git diff --name-only HEAD~5 2>/dev/null | head -20 || echo "no recent commits"

If PHP files were changed:

1. Run vendor/bin/pint --dirty --format agent — fix any formatting issues.
2. Run php artisan test --compact — all tests must pass.
3. If either fails, STOP. Fix the issues before closing. Do not close with failing tests or dirty formatting.

If no code was changed, skip to Step 3.

Step 3: Build the close reason

Examine the recent git history to construct the close reason:

git log --oneline -5 2>/dev/null || echo "no commits"

The reason must include:

• A brief summary of what changed.
• The commit hash(es) or PR reference.

Format: "<summary>. <commit-ref or PR#>"

Step 4: Close the issue

Run: bd close $id --reason="<your constructed reason>"

Step 5: Clean up triage labels

If the issue had any of these triage labels, they must be removed (closing should handle this, but verify):

• needs-triage
• ready-for-agent
• ready-for-human
• needs-info

These are mutually exclusive workflow labels. A closed issue should have none of them.

Step 6: Evaluate QA need

Manual QA IS required if the change involves ANY of:

• User-visible UI changes
• Auth or permission changes
• Data lifecycle changes (create, update, delete of records)
• Clinical workflow changes
• File upload or handling
• Scheduled jobs or cron commands
• High-risk behavior not fully covered by automated tests

Manual QA IS NOT required for:

• Internal refactors with full test coverage
• Config changes
• Documentation-only changes
• Test-only changes

State your determination clearly: either "No manual QA needed — [reason]" or "Manual QA is needed — [reason]."

Step 7: Create QA bead (only if Step 6 determined QA is needed)

Create a QA task with these requirements:

• Same parent as the implementation bead (from Step 1)
• Dependency: discovered-from:$id
• The description MUST specify all of:
  1. What to test: Specific scenarios and user flows.
  2. Role/data setup: What user role, what data must exist.
  3. Expected outcomes: What the tester should see if it works.
  4. How to file failures: Create a bug bead with --deps discovered-from:<qa-bead-id>.

Run: bd create --title="QA: <brief description>" --type=task --priority=2 --description="<full QA spec>"

Then add the dependency: bd dep add <new-qa-id> $id