GitHub Sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
Best use case
GitHub Sync is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
Teams using GitHub Sync should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/github-sync/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How GitHub Sync Compares
| Feature / Agent | GitHub Sync | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GitHub Sync Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships. ## Agent Project Tracker - `project-tracker` ## Workflow 1. Create epic issue with `epic` and `ccpm` labels 2. Create task issues linked to epic with stream-type labels 3. Add acceptance criteria as checkboxes in issue body 4. Set issue relationships (parent/child) 5. Sync progress updates as issue comments 6. Close issues when tasks complete 7. Maintain bidirectional sync state ## Inputs - `githubRepo` - GitHub repository (owner/repo) - `featureName` - Feature identifier - `epic` - Epic document - `tasks` - Task list from decomposition ## Outputs - Epic issue number - Task issue numbers with ID mapping - Labels applied - Sync status report ## Issue States `open` -> `in-progress` -> `blocked` -> `review` -> `closed` ## Process Files - `ccpm-orchestrator.js` - Phase 4 of full lifecycle - `ccpm-parallel-execution.js` - Progress sync during execution - `ccpm-tracking.js` - Tracking data sync
Related Skills
github-actions-web
GitHub Actions for web app CI/CD, testing, and deployment.
asyncapi-docs
AsyncAPI specification handling for event-driven API documentation. Parse, validate, and generate documentation for message-based APIs including Kafka, MQTT, WebSocket, and AMQP systems.
state-sync
State synchronization skill for delta compression and interpolation.
codebase-sync
Convention discovery and rule generation from codebase analysis. Scans project structure, builds search indexes, identifies patterns, and generates enforceable rules.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.