- name
- artifact_testing
- metadata
- { "includeInPrompt": false }
- description
- Verify an artifact before delivering it - file deliverables (pdf, pptx, docx, xlsx, csv) and web artifacts alike. Use whenever a build is about to return a link, or a build task asks for validation, QA, or a visual check. Covers the per-kind gate scripts, render-and-look verification, and leftover-placeholder scanning.
Artifact verification
One home for verification across the artifact namespace. The rule every kind shares: a deliverable is verified by looking at what the user will see, freshly rendered, not by trusting the code that produced it. Never return a link while a gate below fails; after three failed fix attempts, report the specific failure and ask for direction instead of iterating.
File kinds: gates, then eyes
The shared render engine is /opt/hatch/skills/artifacts/scripts/render_audit.mjs;
renders outlast muse.exec's default yield, so size yield_ms past the expected
runtime and read the report file the flags name rather than trusting a
backgrounded command's silence.
Then look. Read every validation PNG or page image with fresh eyes - the generating context sees what it expects, not what rendered. Check first for text overflow or cut-off content, then overlaps, collisions, cramped or uneven spacing, low-contrast text, and template decoration left behind.
Placeholder scan. Before returning, search the deliverable's text for leftover scaffolding: TODO, lorem, placeholder, [insert, xxx runs, and sample rows the user never asked for. Anything found is fixed, not shipped.
Web artifacts
Web builds keep their own audit tools (web_artifacts.build and
web_artifacts.audit run the same capture engine with enforcement); this
skill's render-fresh and placeholder rules apply to their output all the
same.