candid-validate-standards
Technical.md Validator
Analyze a Technical.md file and identify rules that may be ineffective, vague, or redundant with existing tooling.
Workflow
Step 1: Locate Technical.md
Find the Technical.md file to validate:
- If path argument provided → use that path
- Check
./Technical.md - Check
./.candid/Technical.md
If no file found:
❌ No Technical.md found.
Looked in:
More from ron-myers/candid
candid-review
Use when reviewing code changes before commit or PR - provides configurable code review (harsh or constructive tone) with project standards from Technical.md, architectural context, categorized issues with actionable fixes, todo integration for tracking selected issues, and optional automatic commit of applied fixes
55candid-init
Generate Technical.md and config.json by deeply analyzing your codebase structure, architecture, and patterns
54candid-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