From github-issues
Edit, close, reopen, delete, and manage GitHub issues and labels. Use when user says "close issue
How this skill is triggered — by the user, by Claude, or both
Slash command
/github-issues:manageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Modifies existing issues — edit, close, reopen, delete, batch operations, and label management.
Modifies existing issues — edit, close, reopen, delete, batch operations, and label management.
For creating new issues, use /github-issues:create.
skills/shared/references/cross-cutting.mdskills/shared/references/label-taxonomy.md--json flags for structured outputgh auth status
Before executing any issue edit (title, body, labels, assignee, milestone), delegate to the issue-reviewer agent to validate the proposed changes. Present the review results to the user. If the review fails, fix the issues before proceeding.
Modify issue properties with context.
# Edit title
gh issue edit NUMBER --title "New title"
# Edit body
gh issue edit NUMBER --body "New body"
# Add labels
gh issue edit NUMBER --add-label "bug"
# Remove labels
gh issue edit NUMBER --remove-label "chore"
# Set assignee
gh issue edit NUMBER --add-assignee USERNAME
# Remove assignee
gh issue edit NUMBER --remove-assignee USERNAME
# Set milestone
gh issue edit NUMBER --milestone "v2.0"
Always add a comment explaining the change:
gh issue comment NUMBER --body "Updated labels: added \`bug\` — this is a defect in existing behavior, not a missing feature."
Workflow:
gh issue list --search "#NUMBER" --state open --json number,title
# Completed
gh issue close NUMBER --reason completed --comment "Resolved by #PR or description of resolution"
# Not planned
gh issue close NUMBER --reason "not planned" --comment "Reason for not proceeding"
gh issue comment DEPENDENT_NUMBER --body "Note: #NUMBER has been closed. Impact on this issue: ..."
gh issue reopen NUMBER --comment "Reopening — the fix in #PR did not fully resolve the problem. See reproduction steps: ..."
Use with extreme caution. Deletion is irreversible.
# Always warn the user first
gh issue delete NUMBER --yes
Only proceed after explicit user confirmation. Suggest closing instead of deleting in most cases.
For operations across multiple issues, read references/batch-operations.md for safety rules and patterns.
Common batch operations:
List existing labels:
gh label list --json name,color,description --limit 100
Create a label (following taxonomy in skills/shared/references/label-taxonomy.md):
gh label create "LABEL_NAME" --color "HEX" --description "Description"
Edit a label:
gh label edit "OLD_NAME" --name "NEW_NAME" --color "HEX" --description "Description"
Delete a label:
gh label delete "LABEL_NAME" --yes
Rules:
type:, status:, area: patternsIssue creation fails:
gh repo view --json hasIssuesEnabledPermission denied on edit:
gh repo view --json viewerPermissionMilestone not found:
gh api repos/{owner}/{repo}/milestones --jq '.[].title'npx claudepluginhub ondrasek/cc-plugins --plugin github-issuesPerforms administrative operations on GitHub issues: transfer between repos, pin/unpin important ones, lock/unlock discussions, create development branches, bulk label/assign/close/reopen, manage custom fields.
Manage GitHub issues via CLI with bulk operations, JSON/jq parsing, search filters, and issue-to-PR workflow. Also stores AI session context for resuming tasks.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.