원클릭으로
dev-rc
Release candidate preparation. Final checks before merge - QA, security, review, changelog. The last gate before shipping.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Release candidate preparation. Final checks before merge - QA, security, review, changelog. The last gate before shipping.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Read Claude Code documentation to learn about features, capabilities, hooks, skills, MCP, subagents, and how to use Claude Code effectively.
Close a dev-cycle session, capture learnings, and optionally commit. Use when development work is complete and ready to wrap up.
Fully autonomous development mode. Spec in, production-ready software out. Claude makes decisions, uses agents, commits locally. Only stops for hard blockers.
Run QA checks on current work. Tests, linting, type checking, build verification. Use during or after development to catch issues early.
Security audit with Sentinel. Checks for vulnerabilities, secrets, dependencies, and security best practices. Use before shipping or when working on auth/crypto/sensitive areas.
Start or resume a development session. Use when beginning feature work, implementing changes, or continuing previous work. Orchestrates discovery, planning, review, and build phases with Bob and Garry.
| name | dev-rc |
| description | Release candidate preparation. Final checks before merge - QA, security, review, changelog. The last gate before shipping. |
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 Tako:
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 Tako:
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 |