Github Sync
Scannednpx machina-cli add skill a5c-ai/babysitter/github-sync --openclawGitHub Sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
Agent
Project Tracker - project-tracker
Workflow
- Create epic issue with
epicandccpmlabels - Create task issues linked to epic with stream-type labels
- Add acceptance criteria as checkboxes in issue body
- Set issue relationships (parent/child)
- Sync progress updates as issue comments
- Close issues when tasks complete
- Maintain bidirectional sync state
Inputs
githubRepo- GitHub repository (owner/repo)featureName- Feature identifierepic- Epic documenttasks- 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 lifecycleccpm-parallel-execution.js- Progress sync during executionccpm-tracking.js- Tracking data sync
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/ccpm/skills/github-sync/SKILL.mdView on GitHub Overview
GitHub Sync enables bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships. It uses the Project Tracker - project-tracker to align epics with their task issues, capture acceptance criteria, and maintain parent/child relationships, progress updates, and issue state transitions.
How This Skill Works
It creates an epic issue labeled epic and ccpm, then spawns linked task issues with stream-type labels. Acceptance criteria are recorded in the issue body as checkboxes, parent/child relationships are defined, and progress updates are posted as issue comments to maintain bidirectional sync and close issues when tasks complete.
When to Use It
- When planning a new feature, create an epic issue labeled epic and ccpm and align tasks.
- When decomposing an epic into trackable tasks, create linked task issues with stream-type labels.
- When acceptance criteria need to be explicit, add them as checkboxes in the epic/task issue body.
- When tracking progress, post updates as issue comments to keep bidirectional state.
- When tasks are finished, automatically close related issues to reflect completion.
Quick Start
- Step 1: Create epic issue with labels epic and ccpm in the repository.
- Step 2: Create task issues linked to the epic with stream-type labels.
- Step 3: Add acceptance criteria as checkboxes, set parent/child relationships, and monitor progress via comments.
Best Practices
- Use epic and ccpm labels on epic issues.
- Link each task issue to the epic with clear stream-type labels.
- Capture acceptance criteria as checkboxes in the issue body.
- Explicitly set parent/child relationships between related issues.
- Regularly post progress updates as issue comments to maintain bidirectional sync.
Example Use Cases
- Epic: User Onboarding with tasks for Welcome Screen and Email Verification.
- Epic: Payment Integration with tasks for Checkout UI and Stripe Webhook Listener.
- Epic: Dashboard Revamp with tasks for Stats Widgets and Charts Refactor.
- Epic: Mobile App Sync with tasks for Push Notifications and Offline Sync.
- Epic: Audit Logging with tasks for Event Logger and Data Export.
