Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.
日本語の概要は準備中です。原文の説明を表示しています。
The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The final gate. QA passed? Security clean? Ready to ship.
"A release candidate is a promise. Don't make promises you can't keep."
Before running /dev-rc, you should have:
If not done, we'll run them.
# Current state
git status
git log --oneline -5
# What's the diff from main?
git diff main...HEAD --stat
Show the user:
Release Candidate Check
Branch: {branch}
Commits: {N} ahead of main
Files: {N} changed
Lines: +{added} -{removed}
Proceeding with RC checks...
Check if QA was run in last hour:
Must pass to continue.
Check if security audit was run in last hour:
Must pass (CRITICAL/HIGH = 0) to continue.
Delegate to Garry:
"Garry, final review before release.
This is going to main. Check:
1. All requirements met from the dev-cycle session
2. No debug code left behind
3. No TODO/FIXME that should block release
4. Documentation updated if needed
5. Breaking changes documented
Diff: {git diff main...HEAD}
Give me a go/no-go."
Ask the user:
Generate changelog entry?
Based on commits:
{git log main...HEAD --oneline}
Options:
1. Yes, generate for me
2. Yes, I'll write it
3. Skip changelog
If generating:
## [Unreleased]
### Added
- {new features from commits}
### Changed
- {modifications from commits}
### Fixed
- {bug fixes from commits}
## Release Candidate Summary
### Checks
- QA: ✓ PASSED
- Security: ✓ PASSED
- Review: ✓ APPROVED
### Changes
{git diff main...HEAD --stat summary}
### Commits
{git log main...HEAD --oneline}
### Changelog
{generated or provided entry}
---
RC Status: READY
Next steps:
1. /dev-finish - Commit, PR, close cycle
2. Manual review - Look at the diff yourself
3. Hold - Not ready yet
## Release Candidate: NOT READY
### Blockers
- QA: ✗ 2 test failures
- Security: ✓ Passed
- Review: ⚠ TODO found in src/auth.ts
### Required Actions
1. Fix test failures
2. Remove or address TODO
Run /dev-qa to fix tests, then /dev-rc again.
/dev-rc quick
Skip interactive prompts:
With dev-cycle: Final phase before finish With dev-qa: Runs QA if needed With dev-security: Runs security if needed With dev-finish: Natural next step after RC passes
| Check | Tool | Blocker? |
|---|---|---|
| Tests pass | dev-qa | Yes |
| Lint clean | dev-qa | Yes |
| Build works | dev-qa | Yes |
| No critical vulns | dev-security | Yes |
| No high vulns | dev-security | Yes |
| Requirements met | Garry | Yes |
| No debug code | Garry | Yes |
| Docs updated | Garry | No |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.
日本語の概要は準備中です。原文の説明を表示しています。
Look up how Claude Code itself works — hooks, skills, subagents, MCP, plugins, settings — from the official docs, so answers come from the current spec instead of memory.
日本語の概要は準備中です。原文の説明を表示しています。
Design better agents, skills and hooks for Claude Code, checking the current spec instead of guessing at fields.
日本語の概要は準備中です。原文の説明を表示しています。
Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.
日本語の概要は準備中です。原文の説明を表示しています。
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
日本語の概要は準備中です。原文の説明を表示しています。
Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.
日本語の概要は準備中です。原文の説明を表示しています。