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 skill automates the synchronization between local development files and GitHub's issue tracking system. It streamlines the project management workflow by drafting issue titles, descriptions, and sub-tasks directly from local USER-STORY and TASK files, ensuring that your remote project board stays perfectly aligned with your local workspace with minimal manual effort.
Use Cases
- Automated Issue Creation: Transform local requirement documents and task lists into structured GitHub issues and sub-tasks using the GitHub CLI.
- Consistency Management: Maintain a single source of truth by syncing remote GitHub issues with local project files to prevent discrepancies in task tracking.
- Developer Workflow Optimization: Integrate issue management into the coding lifecycle, allowing developers to propose and execute issue updates immediately after creating new features or stories.
| 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).