Capture evidence pack
Skill workingclassbuddha/codexmaxxing/skills/capture-evidence-pack
UI skills for Codex: design passes, browser automation, screenshots, responsive checks, and evidence packs.
npx -y skills add workingclassbuddha/codexmaxxing --skill capture-evidence-packAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Gather proof that work was done and works: test outputs, screenshots, videos, logs, commands, git diff summaries, environment notes, and known risks. Use after code changes, demos, UI work, experiments, bug fixes, repo packaging, or before handing off a branch or pull request.
SKILL.md
1.4 KB, as published. Nobody here has run it
Capture Evidence Pack
Use this skill when the user needs confidence, not just a summary. Evidence should be small, reproducible, and easy to inspect.
Workflow
- Decide the proof target: tests, browser flow, CLI command, render, screenshot, endpoint, or file output.
- Run the narrowest meaningful automated check first.
- Add one product-level smoke test when the work is user-facing.
- Save artifacts under the repo's existing output folder, or
output/evidence/. - Create a short manifest with commands, files, git commit, and known gaps.
- Handoff with pass/fail status and artifact paths.
Good Evidence
- command output from tests or linters
- screenshot of the changed UI
- rendered image/video for visual artifacts
- endpoint response for API/runtime work
- generated file with timestamp and command
- short risk note for anything not tested
Resources
- Read
references/evidence-pack.mdfor handoff format. - Run
scripts/evidence_manifest.py --root <repo> --out output/evidence/manifest.jsonto create a starter manifest.