Verify template
Run project verification from Codex before claiming work is done. Use before marking a phase complete, opening a PR, or saying tests/lint/build pass.From its SKILL.md
npx -y skills add jajupmochi/agent-harness --skill verify-templateAssembled 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.
SKILL.md
1.0 KB, 191 tokens by cl100k_base, as published. Nobody here has run it
verify-template
Read ../general/verify-template/SKILL.md, then adapt it to Codex:
- Prefer commands documented in
AGENTS.md, package manifests, Makefiles, or CI config over generic defaults. - Run only relevant checks for the files changed.
- If a command needs network, dependency installation, or writes outside the workspace, use Codex approval flow.
- Report exact commands run and whether each passed, failed, or was skipped.
- Do not claim success from intended commands or stale output.
For Python, start with uv run ruff check, uv run ruff format --check,
uv run mypy, and uv run pytest when the project supports them.
For Node, start with package scripts such as lint, typecheck, test, and
build. Do not invent scripts that are not in package.json.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.