github-sync

GitHub sync establishes bidirectional synchronization between GitHub Milestones (mapped to Release Plans) and Issues (mapped to RFCs or Tasks), ensuring your SpecWeave docs automatically reflect changes in GitHub and vice versa. Use the /sw-github:sync-spec command to activate syncing after configuring repo, projectId, and sync direction in your spec metadata.

Yes. The Skill provides automated updates that propagate GitHub issue changes to corresponding SpecWeave documents when autoSyncSpecs is enabled in your spec metadata. Configure credentials and sync direction, then the system tracks and applies updates bidirectionally without manual intervention.

Configure spec metadata with your GitHub repo URL, projectId, syncDirection (one-way or bidirectional), and autoSyncSpecs flag. Provide GitHub credentials and ensure the Skill activates only when you ask about GitHub integration or configuration. The Skill guides you through these setup steps and troubleshoots credential or workflow issues.

The Skill focuses on syncing GitHub Milestones and Issues. Issues labeled 'feature' can trigger RFC creation in SpecWeave. While pull requests and detailed label-based workflows are not explicitly covered, the bidirectional sync maintains traceability between GitHub entities and their SpecWeave counterparts.

The Skill relies on syncDirection and metadata configuration to determine update flow. Bidirectional sync maintains consistency by applying changes according to your specified direction. Configure sync direction carefully to avoid conflicts, and the Skill provides troubleshooting guidance when synchronization issues occur.

Yes. The Skill provides traceability links between GitHub entities and their corresponding SpecWeave documents, enabling clear tracking of relationships. These links persist across bidirectional updates, so you always know which GitHub issue or milestone maps to each spec.