name: qa-report description: Open a generated cloudsplaining HTML report and QA it with the dogfood skill, focused on the Privilege Escalation findings. This skill should be used to visually verify a report renders correctly after onboarding a new technique or refreshing fixtures. It writes browser artifacts to a gitignored directory and never persists auth state. allowed-tools: Bash(agent-browser:), Bash(just:), Bash(mkdir:*), Read
QA Report
Visually QA a generated cloudsplaining report in a browser via the dogfood skill.
When to use
- After
just generate-reportorscan-live-account, to confirm the report renders correctly. - As the QA leg of
report-regression-checkandmega-pipeline.
Inputs
- A report to open, one of:
- a local file, e.g. the generated report
file:///<abs path>/index.html(fromjust generate-report) or acloudsplaining scan -o <dir>/output - the dev server:
just serve-js(serves the Vue report at the printed localhost URL)
- a local file, e.g. the generated report
- An output directory for browser artifacts. Default to a gitignored location:
- example-data runs →
dogfood-output/ - live-account runs → inside the scan's
.live-scans/<...>/dogfood/directory
- example-data runs →
Workflow
- Ensure the report exists (
just generate-reportfor example data, or it was produced byscan-live-account). - Invoke the
dogfoodskill against the report URL. Pass:- Output directory: the gitignored path above, so screenshots/videos never land in tracked paths.
- Scope: "Focus on the Privilege Escalation section: every finding's method name (
type) and its IAMactionsrender; the readthedocs links resolve; severity badges and per-category counts are correct; the summary chart matches the findings."
- Do NOT run
agent-browser ... state saveor persistauth-state.json— the report is static and needs no login. - Summarize the dogfood findings (rendering bugs, missing data) and where the artifacts were written.
Notes
- Never write browser artifacts into tracked repo paths.
dogfood-output/and.live-scans/are gitignored. - For a regression comparison of old vs new reports, use the
report-regression-checkskill (which calls this one).