agf-running-release-retro
Use when product-lead is about to run a release retrospective after a successful MAJOR or MINOR release push (PATCH skipped). Provides applicability gate, pre-conditions, 7-step execution sequence, anti-patterns, and the verification gate before commit. Pairs with template docs/reviews/retro-_TEMPLATE.md and slash /agf-release-retro.
npx skills add pcliangx/AppGenesisForge --skill agf-running-release-retro --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Running Release Retrospective Use this skill when: - product-lead has just pushed a MAJOR (`vX.0.0`) or MINOR (`vX.Y.0`) release tag and created the GitHub release - The user typed `/agf-release-retro vX.Y.Z` and the slash dispatched here ## Applicability — PATCH is excluded **Parse `vX.Y.Z`** to gate execution: > retro 是 release 后的**建议复盘(非强制 gate,见 versioning.md step 7)**;本 skill 在用户主动触发 `/agf-
What does the agf-running-release-retro skill do?
Use when product-lead is about to run a release retrospective after a successful MAJOR or MINOR release push (PATCH skipped). Provides applicability gate, pre-conditions, 7-step execution sequence, anti-patterns, and the verification gate before commit. Pairs with template docs/reviews/retro-_TEMPLATE.md and slash /agf-release-retro.
How do I install it?
Run `npx skills add pcliangx/AppGenesisForge --skill agf-running-release-retro --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From pcliangx/AppGenesisForge, a repository with 359 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.