How do I install the Gh Issues skill?

Run npx skillmds@latest add claude-world/gh-issues 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 Gh Issues 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 Gh Issues?

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 Gh Issues free to use?

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

Who published Gh Issues?

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

Gh Issues by claude-world — Agent Skill

Name: Gh Issues
Author: claude-world

Gh Issues

Auto-fix GitHub issues by fetching open issues, spawning agents to implement fixes, and opening PRs. Monitors PR review comments. Use when user says "fix github issues", "auto-fix bugs", "work through issues on repo X".

claude-world d71fe43 2.3 KB Updated Sep 17, 2026

File contents

GitHub Issues Auto-Fixer

Fetch GitHub issues, implement fixes, and open PRs — all automated.

Prerequisites

gh CLI installed and authenticated: brew install gh && gh auth login
Or: GH_TOKEN environment variable set

Process

1. Fetch Issues

# List open issues (default: bug label, limit 5)
gh issue list --repo <owner/repo> --label bug --limit 5 --json number,title,body,labels

2. For Each Issue

Read the issue body and comments for reproduction steps
Clone/navigate to the repo
Create a feature branch: git checkout -b fix/issue-<number>
Implement the fix (read code, understand context, make changes)
Run tests if available
Commit with message: fix: <description> (closes #<number>)
Push and create PR:

gh pr create --repo <owner/repo> \
  --title "fix: <title>" \
  --body "Closes #<number>\n\n## Changes\n- <description>"

3. Monitor PRs (optional --watch flag)

# Check for review comments
gh pr view <number> --repo <owner/repo> --json reviewDecision,reviews,comments

Address review feedback and push updates.

Commands Reference

Command	Purpose
`gh issue list --repo R --json number,title,body`	List open issues
`gh issue view N --repo R --json body,comments`	Read issue details
`gh pr create --repo R --title T --body B`	Create PR
`gh pr view N --repo R --json reviews,comments`	Check PR reviews
`gh pr merge N --repo R --squash`	Merge PR (with user approval)

Usage Examples

/gh-issues octocat/hello-world --label bug --limit 3
/gh-issues my-org/api --label "good first issue" --dry-run
/gh-issues owner/repo --watch (monitor and address PR reviews)

Rules

Always check if gh is installed first
Never merge PRs without explicit user approval
Create one PR per issue (not batch)
Run existing tests before creating PR
If fix is unclear, comment on the issue asking for clarification instead of guessing
Dry-run mode: show what would be done without making changes

---name: gh-issuesdescription: Auto-fix GitHub issues by fetching open issues, spawning agents to implement fixes, and opening PRs. Monitors PR review comments. Use when user says "fix github issues", "auto-fix bugs", "work through issues on repo X".---# GitHub Issues Auto-FixerFetch GitHub issues, implement fixes, and open PRs — all automated.## Prerequisites- `gh` CLI installed and authenticated: `brew install gh && gh auth login`- Or: `GH_TOKEN` environment variable set## Process### 1. Fetch Issues```bash# List open issues (default: bug label, limit 5)gh issue list --repo <owner/repo> --label bug --limit 5 --json number,title,body,labels```### 2. For Each Issue1. Read the issue body and comments for reproduction steps2. Clone/navigate to the repo3. Create a feature branch: `git checkout -b fix/issue-<number>`4. Implement the fix (read code, understand context, make changes)5. Run tests if available6. Commit with message: `fix: <description> (closes #<number>)`7. Push and create PR:```bashgh pr create --repo <owner/repo> \ --title "fix: <title>" \ --body "Closes #<number>\n\n## Changes\n- <description>"```### 3. Monitor PRs (optional --watch flag)```bash# Check for review commentsgh pr view <number> --repo <owner/repo> --json reviewDecision,reviews,comments```Address review feedback and push updates.## Commands Reference| Command | Purpose ||---------|---------|| `gh issue list --repo R --json number,title,body` | List open issues || `gh issue view N --repo R --json body,comments` | Read issue details || `gh pr create --repo R --title T --body B` | Create PR || `gh pr view N --repo R --json reviews,comments` | Check PR reviews || `gh pr merge N --repo R --squash` | Merge PR (with user approval) |## Usage Examples- `/gh-issues octocat/hello-world --label bug --limit 3`- `/gh-issues my-org/api --label "good first issue" --dry-run`- `/gh-issues owner/repo --watch` (monitor and address PR reviews)## Rules- Always check if `gh` is installed first- Never merge PRs without explicit user approval- Create one PR per issue (not batch)- Run existing tests before creating PR- If fix is unclear, comment on the issue asking for clarification instead of guessing- Dry-run mode: show what would be done without making changes

Frequently asked questions