candid-chrome-qa
Candid Chrome QA
Drive a real Chrome session against a running web app, find issues, and write structured findings to disk for downstream triage. Part of the Candid plugin's QA workflow — sits alongside /candid-review (code) and /candid-ship (release).
This is a technique skill. Follow the order. The schema is non-negotiable.
Inputs
When invoked, the user provides (or you confirm):
- goal — surface to test, e.g. "Agent Config / AI Setup, all 16 tabs". Skipped if
--goal "<text>"is passed. - prompt — free-form QA plan (what to exercise, edge cases, hot spots). Skipped if
--prompt "<text>"is passed. - app URL — usually
http://localhost:<port>. Verify before you start. Skipped if the user passes--urlorchromeQA.defaultUrlis set in.candid/config.json.
CLI flags (full set):
| Flag | Purpose |
|---|---|
--url <url> |
Provide the app URL up front, skipping the prompt. |
--goal "<text>" |
Pre-fill the goal prompt. Skip the interactive ask. |
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-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
11