github-issue
Manage GitHub issues - fetch details, update descriptions, add comments, close issues. Use when working with GitHub issues, reviewing issue status, or tracking implementation progress.
When & Why to Use This Skill
This Claude skill empowers developers to manage GitHub issues directly within their AI-assisted workflow. By leveraging the GitHub CLI, it enables fetching real-time issue data, updating descriptions, adding structured progress comments, and closing tasks. It bridges the gap between coding and project tracking, ensuring that issue statuses and documentation remain accurate and up-to-date with minimal manual effort, significantly boosting developer productivity and team transparency.
Use Cases
- Progress Tracking: Post structured status updates using templates to indicate if a task is in progress, blocked, or ready for review.
- Issue Maintenance: Quickly update issue descriptions to incorporate new requirements or technical findings discovered during the development process.
- Workflow Automation: Close completed issues with comprehensive summaries, including links to Pull Requests and testing results, to maintain a clean project board.
- Context Retrieval: Fetch and review issue details, labels, and existing comments to gain full context before starting a new implementation task.
| name | github-issue |
|---|---|
| description | Manage GitHub issues - fetch details, update descriptions, add comments, close issues. Use when working with GitHub issues, reviewing issue status, or tracking implementation progress. |
| allowed-tools | Bash(gh:*), Read, Write |
GitHub Issue Management
Manage GitHub issues via gh CLI.
Core Commands
# Fetch issue details
gh issue view <number> --json number,title,body,state,labels,comments
# Update description
gh issue edit <number> --body "$(cat <<'EOF'
Updated description...
EOF
)"
# Add comment
gh issue comment <number> --body "$(cat <<'EOF'
## Progress Update
**Status:** [analyzing|in_progress|blocked|ready_for_review]
- Point 1
- Point 2
EOF
)"
# Close issue
gh issue close <number> --reason completed
Comment Templates
Implementation Analysis:
## Implementation Analysis
**Already implemented:** [list]
**Test coverage:** [list]
**Still needed:** [list]
Completion Summary:
## Implementation Complete
PR: #<number>
**Changes:** [summary]
**Testing:** [how tested]
Best Practices
- Add comments to track progress
- Use structured format (headers, lists)
- Reference related PRs and issues
- Keep description current with requirements