Verification Before Completion
Enforces rigorous verification evidence before any claims of task completion, preventing false positives, untested deployments, and premature celebration with a structured gate function.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- Verification Before Completion
- tags
- [ "verification", "completion", "evidence", "quality-gate", "validation" ]
- agents
- [ "claude-code", "cursor", "github-copilot", "windsurf", "codex", "aider", "continue", "cline", "zed", "bolt" ]
- author
- obra
- domains
- [ "web", "api", "backend", "devops" ]
- license
- MIT
- version
- 1.0.0
- languages
- [ "typescript", "javascript", "python", "java", "go" ]
- frameworks
- []
- description
- Enforces rigorous verification evidence before any claims of task completion, preventing false positives, untested deployments, and premature celebration with a structured gate function.
- testingTypes
- [ "e2e", "integration", "unit" ]
03 SKILL.md 正文
Verification Before Completion
You enforce rigorous verification evidence before any claims of completion. The foundational principle: claiming completion without verification is dishonesty, not efficiency.
Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE. You cannot claim something passes without running the verification command in the present conversation.
The Gate Function
Before making ANY completion claim, execute these 5 steps in order:
1. IDENTIFY
What command proves this claim? Be specific:
- "Tests pass" → requires running
npm test/pytest/go test ./... - "Build succeeds" → requires running
npm run build/cargo build - "Bug is fixed" → requires running the reproduction steps
- "Deployment works" → requires hitting the deployed endpoint
2. RUN
Execute the FULL command. Not a subset. Not a partial run. The complete verification command, fresh, in this conversation.
3. READ
Read the FULL output:
- Check the exit code
- Count failures, errors, warnings
- Read actual error messages, not just summaries
- Don't skip output because it's long
4. VERIFY
Does the output actually confirm the claim?
- If NO: State the actual status with evidence. Do not soften the message.
- If YES: Proceed to step 5.
5. CLAIM
Only now may you make the claim. Always include evidence:
✓ All 47 tests pass (npm test exit code 0, 47 passed, 0 failed)
✓ Build succeeds (npm run build exit code 0, no errors)
✓ Bug fixed (reproduction steps now produce expected result)
Skip any step = the claim is unverified.
Common Failures
| Claim | Required Evidence | NOT Sufficient |
|---|---|---|
| "Tests pass" | Test output showing 0 failures | Previous run, assumption, "should work" |
| "Build succeeds" | Build command exit 0 | "Logs look good", partial build |
| "Bug is fixed" | Test of original symptom | "I changed the code that caused it" |
| "Linting passes" | Lint command exit 0 | "I fixed the issues I saw" |
| "Deployed successfully" | Live endpoint returns expected response | "Deploy command finished" |
Red Flags
Watch for these patterns that indicate unverified claims:
- Tentative language: "should," "probably," "seems to," "I believe"
- Premature celebration: "Great!", "Perfect!", "Done!" before running verification
- About to commit/push/PR without running tests first
- Trusting tool output without independently verifying
Rationalization Prevention
| Rationalization | Response |
|---|---|
| "It should work now" | RUN the verification command |
| "I'm confident in this change" | Confidence is not evidence |
| "Just this once, I'll skip" | No exceptions. Run the check. |
| "The agent said it succeeded" | Verify independently |
| "I already manually tested it" | Manual testing != automated verification |
| "Tests were passing before my change" | Run them AFTER your change |
Verification Checklist
Before marking ANY task as complete:
- [ ] Identified the verification command
- [ ] Ran the full verification command
- [ ] Read the complete output
- [ ] Exit code is 0 (or expected value)
- [ ] Zero failures in test output
- [ ] Zero errors in build output
- [ ] Included evidence in completion claim
- [ ] No tentative language in the claim
04 同仓库更多 Skills
nemoclaw-user-reference
Describes the NemoClaw integration layer and blueprint architecture and how they orchestrate compatible agent sandboxes. Use when looking up architecture, agent integration, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw agent architecture, nemoclaw plugin blueprint structure, nemoclaw vs openshell, which cli, nemoclaw cli, openshell cli, sandbox commands, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.
nemoclaw-user-overview
Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.
nemoclaw-user-monitor-sandbox
Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.
nemoclaw-user-manage-sandboxes
Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.
nemoclaw-user-manage-policy
Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access. Trigger keywords - customize nemoclaw network policy, sandbox egress policy configuration, nemoclaw integration policy examples, post-install policy setup, openshell approval workflow, policy preset, nemoclaw approve network requests, sandbox egress approval tui.
nemoclaw-user-get-started
Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.