release
Release
Use this skill for repos that publish from GitHub Releases and want human-written notes instead of GitHub's generated summary.
Guardrails
- Prefer the repo's default branch from
gh repo view; do not guess. - Start from a clean working tree. If tracked files are dirty, stop and ask before continuing.
- If the current branch is not the default branch, stop and ask before switching.
- Fetch before planning:
git fetch origin --tags. - Fast-forward the default branch before editing:
git pull --ff-only origin <default-branch>. - Never force-push the default branch.
- Never use GitHub generated release notes for this workflow.
- Always create the release tag with a leading
v, for examplev0.6.0. - Always pin the release to the exact changelog commit SHA with
gh release create --target <sha>. - If
origin/<default-branch>moves after planning or before pushing, stop and regenerate the release plan.
Helper Script
More from pwrdrvr/ghcrawl
ghcrawl
Use the local ghcrawl CLI to inspect duplicate clusters and issue/PR summaries from the existing ghcrawl dataset, and refresh one repo only when the user explicitly asks. Use when a user wants to triage related issues or PRs, inspect semantic clusters, or run ghcrawl's staged refresh pipeline.
11project-manager
Manage GitHub issues and the GitHub Project board for the current repository, while keeping the local tracker in sync. Use when the user wants to capture freeform requirements as issues, flesh out issue descriptions from repo or upstream research, triage Priority/Size/Workflow/Status, add issues or PRs to the repo's configured project board, or reconcile GitHub state with `.local/work-items.yaml`.
1