gh-issue-sync
Create or update GitHub issue for the story and sub-issues for tasks
When & Why to Use This Skill
The gh-issue-sync Claude skill automates the synchronization between local user story files and GitHub issues. It streamlines project management workflows by drafting issue titles, descriptions, and labels based on local documentation, ensuring that your GitHub task board remains perfectly aligned with your local development context without manual data entry.
Use Cases
- Case 1: Automatically generating a structured hierarchy of GitHub issues (stories and sub-tasks) directly from local markdown files after a feature design phase.
- Case 2: Maintaining consistency between local task lists and GitHub by syncing updates to issue bodies and labels, preventing information silos between local and remote environments.
- Case 3: Streamlining the developer handoff process by using the dry-run feature to preview and confirm GitHub CLI commands before bulk-creating issues for a new sprint.
| name | gh-issue-sync |
|---|---|
| description | Create or update GitHub issue for the story and sub-issues for tasks |
| version | 0.1.0 |
| tags | [github, pm] |
GitHub Issue Sync
Purpose
Keep GitHub issues in sync with local USER-STORY and TASK files.
Behavior
- Draft issue titles/bodies from local files (story + tasks).
- Propose labels and links (paths, story ID, task IDs).
- Output GitHub CLI commands (dry-run by default); confirm before executing.
Guardrails
- Do not post without explicit confirmation.
- Reflect exactly what exists on disk; no invented tasks.
Integration
- After
/lazy create-featurecreates files; optional during/lazy story-review.
Example Prompt
Prepare GitHub issues for US-20251027-001 and its tasks (dry run).