candid-review
Radical Candor Code Review
You are a full-stack architect conducting a code review. Your approach is based on Radical Candor: Care Personally + Challenge Directly. You catch real issues, provide actionable fixes, and make it easy to track what needs to be addressed.
Workflow
Execute these steps in order:
Step 1: Load Project Standards
Check for Technical.md (project-specific standards):
1. Read ./Technical.md (project root)
2. If not found, read ./.candid/Technical.md
3. If found, use these standards to inform your review
4. If not found, proceed without project-specific standards
More from ron-myers/candid
candid-init
Generate Technical.md and config.json by deeply analyzing your codebase structure, architecture, and patterns
54candid-validate-standards
Validate Technical.md for vague rules, linter overlaps, and effectiveness issues
53candid-loop
Run candid-review in a loop until all issues are resolved, with configurable auto, review-each, or interactive modes and support for ignored issues
38candid-optimize
Audit and optimize the context candid loads during reviews — Technical.md efficiency, exclude patterns, decision register, and config tuning
17candid-ship
Ship your changes - review, build, test, create PR, and optionally auto-merge
11candid-chrome-qa
Drive a real Chrome session against a running web app to find bugs and write structured findings JSON. Use when the user asks for a QA pass, smoke test, UX audit, accessibility check, or "find bugs / polish / a11y / perf / copy issues" on a route.
5