github-sync
The github-sync skill enables bidirectional synchronization between project management epics and tasks with GitHub issues, automatically mapping epic documents and task lists to GitHub issues with appropriate labels, relationships, and state transitions. Use this when implementing full-lifecycle project tracking that requires maintaining consistency between internal project documentation and GitHub's issue management system across planning, execution, and completion phases.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/github-sync && cp -r /tmp/github-sync/library/methodologies/ccpm/skills/github-sync ~/.claude/skills/github-syncSKILL.md
# 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
Coordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
>-
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.