Resolve GitHub Issues Systematically

Provides an 8-step GitHub issue resolution workflow driven by an issue ID or URL argument. Analysis and triage - pulling full issue details and metadata, reviewing linked PRs and related issues, searching for similar resolved issues, and checking recent commits or PR history for regression likelihood. Investigation and root-cause analysis via git bisect, including an automated bisect with a test script, blame analysis on the specific file, and searching for all occurrences, imports, and call-hierarchy usages of the problematic function. Branch strategy covering naming conventions for feature, bug-fix, hotfix, and experimental or spike branches, upstream tracking, local branch protection, and linking the branch to the issue for GitHub integration. Implementation planning that breaks the fix into a day-by-day phase plan - foundation, core logic, integration, testing and polish - posted as an issue comment after each subtask. Test-driven development with a pytest integration-test example, followed by code implementation patterns for the actual fix. Pull request creation - a pre-PR checklist running tests, lint, and type-check, grepping staged diffs for stray console.log calls and sensitive data like passwords or tokens, then a gh pr create command with a structured Summary, Changes Made, Testing, Performance Impact, and Checklist body, plus a companion .github/pull_request_template.md with a Related Issue, Type of Change, and Review Checklist. Post-implementation verification - checking deployment status, monitoring error rates post-deploy, verifying the fix in production, and closing the issue with a resolution comment and reference. Three worked reference examples cover a P0 production login bug resolved via git bisect and a hotfix branch, a feature implementation broken into schema, API, and testing sub-tasks, and a complex investigation ending in a performance fix.

Use it when triaging a GitHub issue, investigating root cause with bisect or blame, planning a multi-phase implementation, writing tests before the fix, or creating a pull request that closes the issue. Skip it for anything unrelated to GitHub issue resolution or outside this scope.

Input is a GitHub issue ID or URL; output is a full resolution trail - a triage summary, a root-cause finding, a branch with a TDD-implemented fix, a structured pull request linked to the issue, and a post-merge verification and closing comment.

Built around the GitHub CLI (gh pr create with title, body, base, head, assignee, and label flags), git (bisect, blame, branch naming and upstream tracking), and a project's own test, lint, and type-check commands (npm test, npm run lint, npm run type-check in the examples). Uses a .github/pull_request_template.md for consistent PR structure.

Engineers resolving GitHub issues who want a repeatable, professional workflow from triage through a merged, verified pull request rather than an ad hoc fix-and-push approach.