ais.github.sync

Synchronize AIS specification hierarchies with GitHub issues, milestones, and labels.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-github-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ais.github.sync
Source: https://github.com/AIS-Commercial-Business-Unit/CBU_Specify/tree/main/.cursor/skills/ais.github.sync
Command: npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-github-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill synchronizes the AIS spec hierarchy with GitHub milestones, issues, and labels, ensuring bidirectional tracking and consistency between the two systems.

Core Features & Use Cases

  • GitHub Synchronization: Maps AIS specifications to GitHub milestones, issues, and labels, maintaining synchronization.
  • User Story to Issue Mapping: Converts user stories into GitHub issues, embedding task checklists within the issue body.
  • Full Sync, Push, Pull, and Status Modes: Offers flexible synchronization options for full sync, pushing updates to GitHub, pulling updates from GitHub, and checking sync status.
  • Sub-spec Handling: Supports synchronization of sub-specs independently, ensuring each sub-spec has its own scope.

Quick Start

Run /ais.github.sync <push|pull|status> to synchronize GitHub issues with the local spec hierarchy.

Frequently Asked Questions about ais.github.sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync local specifications with GitHub issues and milestones?

To sync local specifications with GitHub issues and milestones, run the bidirectional synchronization command and choose push, pull, or status modes to map AIS spec hierarchies to GitHub items.

Can I convert user stories into GitHub issues with task checklists?

Yes, you can convert user stories into GitHub issues. The synchronization process automatically embeds task checklists within the issue body during the mapping and push operations.

Does bidirectional sync support independent synchronization for sub-specs?

Yes, bidirectional sync supports independent sub-spec handling. Each sub-spec maintains its own scope during synchronization, ensuring granular tracking between AIS specifications and GitHub items.

What is the difference between push, pull, and status synchronization modes?

Push mode sends local specification updates to GitHub, pull mode retrieves GitHub issue updates locally, and status mode checks the current synchronization state without altering data.

How do I check the sync status between AIS specs and GitHub?

To check the sync status between AIS specs and GitHub, run the synchronization command with the status mode. This evaluates current mapping consistency without pushing or pulling updates.

What is the best way to manage code and issue tracking consistency across GitHub and local spec hierarchies?

The best way to manage code and issue tracking consistency is using full bidirectional sync. This maps local specification hierarchies to GitHub milestones and issues, ensuring continuous tracking alignment.