ron-myers
9 verified skills145 total stars
candid-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.
development17
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
development16
candid-fast-ship
Fast ship for low-risk changes — runs only the steps you explicitly enable in fastShip config
testing16
candid-validate-standards
Validate Technical.md for vague rules, linter overlaps, and effectiveness issues
development16
candid-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
tools16
candid-optimize
Audit and optimize the context candid loads during reviews — Technical.md efficiency, exclude patterns, decision register, and config tuning
testing16
candid-ship
Ship your changes - review, build, test, create PR, and optionally auto-merge
development16
candid-chrome-qa-fix
Take a candid-chrome-qa findings JSON, let the user pick which findings to fix, and dispatch fixes — single batched PR, one PR per finding via Conductor deep links, local-only, or issues-only. Optionally files Linear (or other tracker) issues per finding before shipping.
testing16
candid-init
Generate Technical.md and config.json by deeply analyzing your codebase structure, architecture, and patterns
development16