github-issue-solverlisted

# GitHub Issue Solver Solve GitHub issues end-to-end: triage → explore → design → implement → test → PR → merge → close. **Never guess architecture. Never close an issue before the PR is merged.** --- ## Activation Criteria Invoke this skill when: - User says `/github-issue-solver` or `/solve-issue` - User says "solve issue #N", "fix GitHub issue #N", "work on issue #N" - User pastes a GitHub issue URL - User asks to process open issues from the repository --- ## Workflow ### Step 1 — Fetch Issue Metadata ```bash gh issue view <number> --json title,body,labels,milestone,assignees,comments,url,state,linkedBranches ``` Capture and record: - Title and full body - Labels (bug, feature, security, docs, performance, DX, auth, database, workflow, battle, CLI, mobile, web) - Milestone and due date - All comments (may contain constraints or partial solutions) - Linked PRs or branches If no issue number is provided, ask the user which issue(s) to target. ### Step 2 — Check for Duplicates and Related Work ```bash gh issue list --state all --search "<key terms from title>" gh pr list --state all --search "<key terms>" ``` If a duplicate exists: comment on the issue linking the canonical one, then stop. ### Step 3 — Repository Exploration Do not assume architecture. Explore: ``` apps/* — entry points and composition roots libs/domain/* — business concepts, invariants, core types libs/api/* — contracts and DTOs libs/data/*