// Prints a quick reference for the sync skill suite (sync-status, sync-execute). Use when the user asks how to use the sync skills or needs a reminder of the workflow.
Writes and reviews GitHub Actions workflows with security hardening. Use when creating, modifying, or reviewing .github/workflows/*.yml or .github/actions/*/action.yml files. Covers shell injection prevention, trust gating for fork PRs, action pinning, and secrets hygiene.
Generate a PR title and description for cardano-parts releases by analyzing commit diffs on the current branch. Use when the user asks to write, draft, or generate a PR description, release notes, or changelog for this repo.
Walks through each changed file one at a time, showing the diff and asking the user whether to apply it. Requires "upstream" or "downstream" argument. Use after sync-status to begin applying changes between cardano-parts templates and downstream repos.
Shows a summary table of divergence between cardano-parts templates and configured downstream repos, with per-file one-liner descriptions. Use to get a quick overview of sync state before or during a sync cycle.
| name | sync-help |
| description | Prints a quick reference for the sync skill suite (sync-status, sync-execute). Use when the user asks how to use the sync skills or needs a reminder of the workflow. |
Output the following help text:
/sync-status — See which downstream repos have diverged from templates./sync-execute upstream — Walk through each change, decide whether to
upstream it into templates. One file at a time, with commit pauses./pr-description — Generate the PR description for the upstream changes./sync-execute downstream — Walk through each template change, decide
whether to downstream it. One file at a time, with commit pauses.Always complete all upstreaming and the PR description before downstreaming.
Copy the example config and fill in your downstream repo paths:
cp .ai/skills/sync-review/sync-config.example.json .ai/skills/sync-review/sync-config.local.json
Paths can be relative (from repo root) or absolute. The config is gitignored.
During /sync-execute, the AI shows each diff and waits for your decision:
Each repo in the config has two arrays for persistent decisions:
"exclude" — glob patterns for files to silently skip (e.g., "mdbook/**")"rules" — auto-classify specific files or hunks with a reasonThese are saved per-repo in sync-config.local.json and automatically applied
in future sync cycles.
.ai/skills/sync-review/)| File | Purpose |
|---|---|
sync-config.local.json | Repo paths, excludes, classification rules |
/sync-execute requires a direction: upstream or downstream./sync-status is read-only and safe to run anytime.