Dev rc

Skill ToruAI/toru-claude-agents/skills/dev-rc

Multi-agent team for Claude Code: 7 AI specialists (strategy, dev, security, sales, design, data, research) that collaborate and challenge you. Dev-cycle workflow with machine-verifiable completion.

Install

npx -y skills add ToruAI/toru-claude-agents --skill dev-rc

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.

SKILL.md

3.4 KB, as published. Nobody here has run it

Dev RC - Release Candidate

The final gate. QA passed? Security clean? Ready to ship.

Philosophy

"A release candidate is a promise. Don't make promises you can't keep."

Prerequisites

Before running /dev-rc, you should have:

✓ Code complete
✓ Tests passing (/dev-qa)
✓ Security audit clean (/dev-security)

If not done, we'll run them.

Flow

1. Pre-flight Check

# 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...

2. Run QA (if not recent)

Check if QA was run in last hour:

If yes: Skip, show previous results
If no: Run /dev-qa quick

Must pass to continue.

3. Run Security (if not recent)

Check if security audit was run in last hour:

If yes: Skip, show previous results
If no: Run /dev-security quick

Must pass (CRITICAL/HIGH = 0) to continue.

4. Final Code Review

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."

5. Changelog Entry

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}

6. RC Summary

## 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

7. If Checks Fail

## 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.

Quick Mode

/dev-rc quick

Skip interactive prompts:

Auto-run QA quick
Auto-run security quick
Auto-generate changelog
Show summary only

Integration

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

RC Checklist

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

Agent Roles

Garry: Final approval, completeness check
Bob: Fixes any last-minute issues
Sentinel: Security gate (via dev-security)
Arlo: Data validation if applicable