ワンクリックで
fabrizioduroni-release-prep
Pre-release checklist — verify changelog, lint, build, and version bump before running npm run release
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Pre-release checklist — verify changelog, lint, build, and version bump before running npm run release
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate the full code SDLC for chicio-blog — explore → brainstorm → implement ⇄ review → PR (feature mode), or investigate → confirm → implement ⇄ review → PR (fix mode). Interactive (two human gates) or --autonomous (issue-as-contract, async label gates, PR-only, never merges). Code work only.
The producer side of the autonomous SDLC loop — runs deterministic code-health scanners (coverage, hygiene, a11y), dedups findings against open issues, and files loop-task issues (WITHOUT loop:ready — you curate) for the loop to drain. Session-bound, code work only.
Brainstorm a code idea into a high-confidence, loop-ready GitHub issue for chicio-blog — optionally explore the codebase, grill the idea to shared understanding, synthesize the loop-task contract, and file it via gh. The async front-half of the SDLC pipeline. Code work only.
Scaffold a new blog post with correct directory structure, frontmatter, and opening template
The self-feeding autonomous loop — one tick either discovers work (scout, auto-approved) when the queue is empty or drains one loop:ready issue to a PR. Sequential (no port collision), session-bound, code-only, never merges.
One tick of the autonomous SDLC loop — pick the oldest loop:ready GitHub issue, hand it to the orchestrator's --autonomous mode, and report. Meant to be driven by /loop. Session-bound, code work only.
| name | fabrizioduroni-release-prep |
| description | Pre-release checklist — verify changelog, lint, build, and version bump before running npm run release |
| user_invocable | true |
Run this before npm run release to verify everything is ready.
git status
Verify no uncommitted changes. If there are, warn the user and stop.
Read package.json to get the current version. Then check the latest git tag:
git describe --tags --abbrev=0
Show commits since the last tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Based on conventional commit prefixes, predict the version bump:
feat: commits → minor bumpfix: commits → patch bumpBREAKING CHANGE or !: → major bumpTell the user what version the release would produce.
npm run lint
npm run build
Both must pass.
gh run list --limit 1 --branch main
Verify the latest CI run on main passed.
Summarize:
If everything passes, tell the user they can run npm run release.