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
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement