How do I install the Gh Sync skill?

Run npx skillmds@latest add ao-cyber-systems/gh-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Sync?

AO-Cyber-Systems (@ao-cyber-systems) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Sync by ao-cyber-systems — Agent Skill

Name: Gh Sync
Rating: 4.2 (5 reviews)
Author: AO-Cyber-Systems

Gh Sync

Sync DevFlow planning state to GitHub — create/update objective issues, generate release notes, or push a single objective's state (body + sticky comment + Project v2 fields). Triggers on: "sync to github", "push objectives to github", "github release notes", "sync objective".

File contents

Four modes (parsed from $ARGUMENTS):

objectives (default for empty args) — create/update one issue per roadmap objective, ensure milestone exists
release <tag> — generate release notes from SUMMARY.md files since the previous tag and create or edit the GitHub release
status — report whether GitHub integration is enabled and reachable
sync <objective> (<objective_id>, e.g. 01-github-coordination-layer) — sync ONE objective: rewrite linked issue body to canonical form, upsert sticky state comment in-place, update Project v2 fields (Status, Quarter). Idempotent — safe to run repeatedly.

If $ARGUMENTS does not match objectives, release <tag>, or status, treat it as an objective ID and run the single-objective sync mode.

Run the requested operation:

# Default — sync all objectives (creates/updates issues + milestone)
node ~/.claude/devflow/bin/df-tools.cjs gh sync-objectives

# Release notes for a tag
node ~/.claude/devflow/bin/df-tools.cjs gh sync-release "$TAG"

# Status check
node ~/.claude/devflow/bin/df-tools.cjs gh status

# Sync a single objective's state to its linked GH issue (idempotent)
node ~/.claude/devflow/bin/df-tools.cjs gh sync "$OBJECTIVE_ID"

The single-objective sync (gh sync <objective_id>) is idempotent — running it twice in a row produces no semantic difference on GitHub. The sticky comment uses marker  and is edited in-place (not a new comment). The comment ID is persisted in .planning/.gh-mapping.json so subsequent syncs find the same comment to patch.

If sync-objectives or the single-objective sync created or updated .planning/.gh-mapping.json, commit it:

node ~/.claude/devflow/bin/df-tools.cjs commit "chore: sync GitHub mapping" --files .planning/.gh-mapping.json

Report the result to the user — include issue numbers created/updated, milestone link, release URL, or single-objective sync result (comment action, project fields updated). If the operation was skipped, explain why (disabled, gh not installed, missing github_issue frontmatter, etc.) and how to fix it.

Triggers

Use when the user wants to push DevFlow state to GitHub or recover from a missed sync. Also fires on: "create github issues", "sync state".

---name: gh-syncdescription: Sync DevFlow planning state to GitHub — create/update objective issues, generate release notes, or push a single objective's state (body + sticky comment + Project v2 fields). Triggers on: "sync to github", "push objectives to github", "github release notes", "sync objective".---<objective>One-way push from `.planning/` -> GitHub. Planning files remain authoritative. All operations are no-ops when GitHub integration is disabled or `gh` is not authenticated.Four modes (parsed from $ARGUMENTS):- `objectives` (default for empty args) — create/update one issue per roadmap objective, ensure milestone exists- `release <tag>` — generate release notes from SUMMARY.md files since the previous tag and create or edit the GitHub release- `status` — report whether GitHub integration is enabled and reachable- `sync <objective>` (`<objective_id>`, e.g. `01-github-coordination-layer`) — sync ONE objective: rewrite linked issue body to canonical form, upsert sticky state comment in-place, update Project v2 fields (Status, Quarter). Idempotent — safe to run repeatedly.If $ARGUMENTS does not match `objectives`, `release <tag>`, or `status`, treat it as an objective ID and run the single-objective sync mode.</objective><execution_context>@~/.claude/.planning/config.json</execution_context><process>1. Check `.planning/config.json` for `github.enabled` and `github.repo`. If missing or false, ask the user whether to enable now (offer to set both interactively). Do not proceed without explicit confirmation.2. Run the requested operation:```bash# Default — sync all objectives (creates/updates issues + milestone)node ~/.claude/devflow/bin/df-tools.cjs gh sync-objectives# Release notes for a tagnode ~/.claude/devflow/bin/df-tools.cjs gh sync-release "$TAG"# Status checknode ~/.claude/devflow/bin/df-tools.cjs gh status# Sync a single objective's state to its linked GH issue (idempotent)node ~/.claude/devflow/bin/df-tools.cjs gh sync "$OBJECTIVE_ID"```The single-objective sync (`gh sync <objective_id>`) is idempotent — running it twice in a row produces no semantic difference on GitHub. The sticky comment uses marker `` and is edited in-place (not a new comment). The comment ID is persisted in `.planning/.gh-mapping.json` so subsequent syncs find the same comment to patch.3. If sync-objectives or the single-objective sync created or updated `.planning/.gh-mapping.json`, commit it:```bashnode ~/.claude/devflow/bin/df-tools.cjs commit "chore: sync GitHub mapping" --files .planning/.gh-mapping.json```4. Report the result to the user — include issue numbers created/updated, milestone link, release URL, or single-objective sync result (comment action, project fields updated). If the operation was skipped, explain why (disabled, gh not installed, missing github_issue frontmatter, etc.) and how to fix it.</process><context>- The mapping file `.planning/.gh-mapping.json` is the source of truth for objective-to-issue numbers and sticky comment IDs. Commit it.- This skill never edits issues that DevFlow did not create — only those tracked in the mapping.- Failures (network, rate limit, auth expired) never block the user's workflow. They are reported and the planning state remains authoritative.- For automatic syncing, the new-project workflow already calls `gh sync-objectives` after roadmap creation, and the verifier agent calls `gh comment` on verification gaps. This skill is for manual fire / recovery.- The single-objective sync (`<objective_id>` mode) requires the objective to have a `github_issue` field in its OBJECTIVE.md frontmatter. If absent, run `objectives` mode first to create the issue, then backfill the `github_issue` field.## TriggersUse when the user wants to push DevFlow state to GitHub or recover from a missed sync. Also fires on: "create github issues", "sync state".</context>

Frequently asked questions