sc-managing-github-issues
GitHub issue lifecycle management with worktree isolation
When & Why to Use This Skill
This Claude skill streamlines the entire GitHub issue lifecycle, from initial discovery to final pull request submission. By leveraging GitHub CLI integration and git worktree isolation, it allows developers to implement fixes in clean, dedicated environments without disrupting their main workspace. It automates fetching issue details, branch management, implementation, testing, and PR creation, significantly reducing context-switching and manual overhead for software engineers.
Use Cases
- Automated Bug Resolution: Quickly address reported bugs by allowing the agent to fetch issue context, implement code changes in an isolated worktree, and verify the fix with automated tests.
- Isolated Feature Development: Manage multiple GitHub issues concurrently using worktree isolation, ensuring that experimental changes for one task do not interfere with the main branch or other ongoing work.
- Seamless Pull Request Workflow: Automate the repetitive steps of committing changes, pushing to remote, and opening a pull request with pre-defined templates once a fix is verified.
- Efficient Issue Triage: List, view, and update GitHub issues directly within the Claude interface to maintain project momentum and keep task metadata synchronized without leaving the development environment.
| name | sc-managing-github-issues |
|---|---|
| version | 0.8.0 |
| description | GitHub issue lifecycle management with worktree isolation |
| entry_point | /sc-github-issue |
Managing GitHub Issues Skill
Manage GitHub issues from listing to fixing to PR creation with clean worktree isolation.
Commands
/sc-github-issue- Main entry point for all issue operations
Agents
sc-github-issue-intake- List and fetch issue detailssc-github-issue-mutate- Create and update issuessc-github-issue-fix- Implement fixes in isolated worktreessc-github-issue-pr- Create pull requests
Operations
--list [--repo owner/repo]- List open issues--create- Create issue interactively--update <id>- Update issue fields--fix --issue <id/url> [--yolo]- Full fix workflow: fetch → confirm → worktree → implement → test → commit → push → PR
Dependencies
- Packages: sc-git-worktree >= 0.6.0 (worktree operations)
- CLI: GitHub CLI (
gh) version 2.0 or higher - Config: Package manifest options (base-branch, branch-pattern, auto-pr)
Configuration
Configuration via manifest options (defaults shown):
options:
base-branch:
type: string
default: "main"
branch-pattern:
type: string
default: "fix-issue-{number}"
auto-pr:
type: boolean
default: true
Users can override in .claude/config.yaml:
packages:
sc-github-issue:
base-branch: develop
branch-pattern: "hotfix/{number}"
auto-pr: false
github:
test_command: "npm test"
pr_template: |
## Summary
Fixes #{issue_number}
Data Contracts
All agents return fenced JSON with v0.4 minimal envelope:
{
"success": true|false,
"data": { /* operation results */ },
"error": null|{
"code": "ERROR.CODE",
"message": "Human readable message",
"recoverable": true|false,
"suggested_action": "What to do next"
}
}
Safety
- Pre-flight
ghCLI auth checks - Approval gates before destructive ops (unless
--yolo) - Test failure prompts
- Actionable error messages with suggested actions
- Worktree isolation prevents contaminating main working directory
Integration with sc-git-worktree
The --fix workflow creates isolated worktrees via the sc-git-worktree skill:
- Create:
sc-worktree-createagent createsfix-issue-{number}worktree - Implement: Fix implemented in isolated directory
- Commit & Push: Changes committed and pushed from worktree
- Cleanup: Manual cleanup via
/sc-git-worktree --cleanupafter PR merge
This ensures the main working directory remains clean during fix implementation.
References
references/github-issue-apis.md- GitHub CLI patternsreferences/github-issue-checklists.md- Workflow checklists