How do I install the Github Issue Resolution skill?

Run npx skillmds@latest add tomevault-io/github-issue-resolution in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Issue Resolution safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Issue Resolution?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Issue Resolution free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Issue Resolution?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Issue Resolution by tomevault-io

Name: Github Issue Resolution
Author: tomevault-io

Github Issue Resolution

Systematic methodology for investigating, implementing, and resolving GitHub issues. Use when triaging bugs, implementing features from issues, or managing the full issue-to-PR lifecycle. Do NOT use for PR review comment resolution (use pr-comment-resolution). Use when this capability is needed.

tomevault-io 3f32fe9 2 files · 3.7 KB Updated Sep 17, 2026

File contents

GitHub Issue Resolution

Issue Analysis and Triage

Initial Investigation

gh issue view $ISSUE_NUMBER --comments
gh issue view $ISSUE_NUMBER --json title,body,labels,assignees,milestone,state
gh issue list --search "similar keywords" --state closed --limit 10
git log --oneline --grep="component_name" -20

Priority Classification

Priority	Criteria
P0/Critical	Production breaking, security vulnerability, data loss
P1/High	Major feature broken, significant user impact
P2/Medium	Minor feature affected, workaround available
P3/Low	Cosmetic issue, enhancement request

Root Cause Analysis

git bisect start
git bisect bad HEAD
git bisect good <last_known_good_commit>
git bisect run ./test_issue.sh

git blame -L <start>,<end> path/to/file.js
rg "functionName" --type js -A 3 -B 3

Branch Strategy

git checkout -b feature/issue-${ISSUE_NUMBER}-short-description
git checkout -b fix/issue-${ISSUE_NUMBER}-component-bug
git checkout -b hotfix/issue-${ISSUE_NUMBER}-critical-fix

Implementation

Incremental Commits

git commit -m "feat(auth): add user validation schema (#${ISSUE_NUMBER})"
git commit -m "test(auth): add unit tests for validation (#${ISSUE_NUMBER})"

PR Creation

gh pr create \
  --title "Fix #${ISSUE_NUMBER}: Clear description of the fix" \
  --body "$(cat <<EOF
## Summary
Fixes #${ISSUE_NUMBER} by implementing proper error handling.

## Changes Made
- Added validation for expired tokens
- Updated unit and integration tests

## Testing
- [x] All existing tests pass
- [x] Added new unit tests
- [x] Manual testing completed

## Checklist
- [x] Code follows project style guidelines
- [x] Self-review completed
- [x] No new warnings introduced
EOF
)" \
  --base main \
  --assignee @me \
  --label "bug,needs-review"

Post-Implementation

gh run list --workflow=deploy
gh issue comment ${ISSUE_NUMBER} \
  --body "Fixed in PR #${PR_NUMBER}. Root cause: improper token validation."
gh issue close ${ISSUE_NUMBER} --comment "Resolved via #${PR_NUMBER}"

Examples

Trigger: "Fix bug from GitHub issue #42" Action: Fetch issue details, reproduce the bug, implement fix, add tests, open PR referencing #42 Result: PR created with Fixes #42 — issue auto-closes on merge

Delivery Checklist

Resolution summary with root cause
Code changes with explanations
Test results and coverage
Pull request with issue linking
Verification steps for reviewers
Rollback plan

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: github-issue-resolutiondescription: Systematic methodology for investigating, implementing, and resolving GitHub issues. Use when triaging bugs, implementing features from issues, or managing the full issue-to-PR lifecycle. Do NOT use for PR review comment resolution (use pr-comment-resolution). Use when this capability is needed.---# GitHub Issue Resolution## Issue Analysis and Triage### Initial Investigation```bashgh issue view $ISSUE_NUMBER --commentsgh issue view $ISSUE_NUMBER --json title,body,labels,assignees,milestone,stategh issue list --search "similar keywords" --state closed --limit 10git log --oneline --grep="component_name" -20```### Priority Classification| Priority | Criteria ||----------|----------|| P0/Critical | Production breaking, security vulnerability, data loss || P1/High | Major feature broken, significant user impact || P2/Medium | Minor feature affected, workaround available || P3/Low | Cosmetic issue, enhancement request |## Root Cause Analysis```bashgit bisect startgit bisect bad HEADgit bisect good <last_known_good_commit>git bisect run ./test_issue.shgit blame -L <start>,<end> path/to/file.jsrg "functionName" --type js -A 3 -B 3```## Branch Strategy```bashgit checkout -b feature/issue-${ISSUE_NUMBER}-short-descriptiongit checkout -b fix/issue-${ISSUE_NUMBER}-component-buggit checkout -b hotfix/issue-${ISSUE_NUMBER}-critical-fix```## Implementation### Incremental Commits```bashgit commit -m "feat(auth): add user validation schema (#${ISSUE_NUMBER})"git commit -m "test(auth): add unit tests for validation (#${ISSUE_NUMBER})"```## PR Creation```bashgh pr create \ --title "Fix #${ISSUE_NUMBER}: Clear description of the fix" \ --body "$(cat <<EOF## SummaryFixes #${ISSUE_NUMBER} by implementing proper error handling.## Changes Made- Added validation for expired tokens- Updated unit and integration tests## Testing- [x] All existing tests pass- [x] Added new unit tests- [x] Manual testing completed## Checklist- [x] Code follows project style guidelines- [x] Self-review completed- [x] No new warnings introducedEOF)" \ --base main \ --assignee @me \ --label "bug,needs-review"```## Post-Implementation```bashgh run list --workflow=deploygh issue comment ${ISSUE_NUMBER} \ --body "Fixed in PR #${PR_NUMBER}. Root cause: improper token validation."gh issue close ${ISSUE_NUMBER} --comment "Resolved via #${PR_NUMBER}"```## Examples**Trigger:** "Fix bug from GitHub issue #42"**Action:** Fetch issue details, reproduce the bug, implement fix, add tests, open PR referencing #42**Result:** PR created with `Fixes #42` — issue auto-closes on merge## Delivery Checklist1. Resolution summary with root cause2. Code changes with explanations3. Test results and coverage4. Pull request with issue linking5. Verification steps for reviewers6. Rollback plan---> Converted and distributed by [TomeVault](https://tomevault.io/claim/jlaws) — claim your Tome and manage your conversions.

Frequently asked questions