GitHub Issue Fix

Core Workflow

Use this skill for open-source upstream issue repair, PR creation, PR CI repair, and PR conflict repair.

1. Preserve local work. Check git status --short, current branch, remotes, and authentication before editing.
2. Read project instructions first: AGENTS.md, CONTRIBUTING*, .github/PULL_REQUEST_TEMPLATE*, .github/workflows/, pre-commit configs, test configs, and language/tooling files.
3. Fetch issue or PR metadata with gh: title, body, labels, assignees, linked PRs, comments, reviews, inline review threads, checks, statuses, and timeline signals.
4. Classify before coding:
   • skip: closed, duplicate, maintainer-owned, already fixed by a PR, or explicitly not wanted.
   • needs-info: insufficient reproduction, unclear expected behavior, private artifacts required, or likely design/RFC work.
   • candidate: narrow root cause, no active owner or existing fix, and at least one local/static/test/CI validation path.
5. Implement the smallest mergeable fix. Avoid unrelated refactors, formatting churn, broad architecture changes, or test weakening.
6. Add focused regression tests where practical. If hardware or large-model validation is required, still add a deterministic unit/meta/static check when possible.
7. Run the PR Quality Gate before committing.
8. Commit with project-required sign-off or trailers. For DCO projects, use git commit -s.
9. Push to a fork and create/update one PR per independent fix. Use a local HTML handoff if PR creation cannot be automated.