Menu
Use when about to claim work is complete, fixed, or passing, or before committing or handing off results.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guide for creating new skills, improving existing skills, and evaluating skill quality. Use this whenever the user wants to turn a workflow into a skill, revise a skill, improve triggering behavior, or add evals and benchmarks for a skill.
Use when reviewing a diff, PR, or patch for bugs, regressions, missing tests, architecture risk, security risk, or reviewability concerns before merge.
Use when starting a repo-grounded task, switching subsystems, or when output quality drops and the agent needs tighter project context from rules, specs, relevant files, examples, and current errors.
Use when implementing or reviewing framework-specific code that should be verified against current official docs, versioned guidance, or source-cited examples rather than memory.
Use when the user explicitly asks Guardian to launch or check an external coding assistant such as Codex, Claude Code, Gemini CLI, or Aider.
Use when the request is about a repo, codebase, implementation, bugfix, or backend-owned coding session that should stay anchored to the active workspace.
| name | verification-before-completion |
| description | Use when about to claim work is complete, fixed, or passing, or before committing or handing off results. |
Evidence before claims.
Do not say work is done, fixed, or passing until you have run the command or check that proves it.
Before making a completion claim:
Completion requires the real proof surface to be green, not just a convenient subset.
Use the phrase full legitimate green as the bar:
In the written response, explicitly use the phrase proof surface when describing the completion bar.
Stop if you are about to say:
without fresh verification evidence in the current turn.
Also stop if:
When working in this GuardianAgent repository, prefer the existing harnesses before inventing ad hoc smoke checks:
scripts/run-code-ui-smoke.sh -> runs node scripts/test-code-ui-smoke.mjsscripts/test-coding-assistant.mjs -> coding assistant and code-session workflow harnessscripts/run-skills-routing-harness.sh -> runs node scripts/test-skills-routing-harness.mjsUse these when the claim depends on the Code UI flow or skill routing behavior.
templates/verification-report.md when you want a durable claim -> evidence -> outcome record.systematic-debugging when you do not yet understand the issue.test-driven-development when the missing proof is a failing or passing test.