一键导入
pr-description
// 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.
// 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.
| name | pr-description |
| description | 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. |
Generate a PR title and description following the established pattern used in this repo's release PRs. Output is written to a local pr-description.md file for review, along with a not-included.md file listing minor changes that were intentionally omitted.
Ask the user three questions before starting:
Identify the base branch this PR targets (usually main). Run:
git log --oneline main..HEAD
Review each commit's diff to understand all changes:
git diff main..HEAD
For large diffs, review commit-by-commit:
git log --oneline main..HEAD
git show <commit-hash>
Draft the PR title and description following the format in FORMAT.md.
Write output files:
pr-description.md — the PR title (as an H1) followed by the full description bodynot-included.md — minor changes you chose to omit (formatting fixes, typo corrections, etc.) so the user can review what was left outflake/colmena.nix, tcpTxOpt).| and :---: column separators.** in the version table ONLY for versions that changed from the previous release.unstable. If there's a problem building the latest unstable, mark it with ** in the table and add a footnote note explaining the workaround.not-included.md.See FORMAT.md for the exact section structure, table format, and examples drawn from previous PRs.
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.
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.
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.
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.