Create a plan to fix a GitHub issue, then implement it locally.
Create a plan to fix a GitHub issue, then implement it locally.
$ARGUMENTS: GitHub issue number or URL.Fetch the GitHub issue:
First, extract the issue number from $ARGUMENTS:
$ARGUMENTS is a number (e.g., 123), use it directly$ARGUMENTS is a URL (e.g., https://github.com/owner/repo/issues/123), extract the issue number from the pathThen fetch the issue:
gh issue view <issue-number> --json title,body,comments,labels,assignees
Sanitize the issue content:
Run the issue body through the sanitization script to remove HTML comments, invisible characters, and other artifacts:
printf '%s' "$ISSUE_BODY" | python3 .claude/skills/fix-issue/scripts/sanitize_issue_markdown.py
This removes:
<!-- ... -->)Analyze the issue:
Explore the codebase:
Determine testing approach:
Consider what kind of testing is appropriate for this change:
Note: Per project guidelines, avoid writing many E2E tests for one feature. Prefer one or two E2E tests with broad coverage. If unsure, ask the user for guidance on testing approach.
IMPORTANT for E2E tests: You MUST run npm run build before running E2E tests. E2E tests run against the built application binary. If you make any changes to application code (anything outside of e2e-tests/), you MUST re-run npm run build before running E2E tests, otherwise you'll be testing the old version.
Create a detailed plan:
Write a plan that includes:
Execute the plan:
If the plan is straightforward with no ambiguities or open questions:
/dyad:pr-push when completeIf the plan has significant complexity, multiple valid approaches, or requires user input:
ExitPlanMode to request approval/dyad:pr-push when complete