Loop Change Verifier
cobusgreyling/loop-engineering
Acts as a skeptical checker for changes an implementer sub-agent made, running the tests, confirming the diff scope and returning approve, reject or escalate to a human.
Evidence before claims, always. An agent skill from xenitV1/claude-code-maestro.
Install Verification Mastery
$ npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install xenitV1/claude-code-maestro verification-mastery --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verification-mastery .claude/skills/verification-mastery && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verification-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/verification-mastery into .claude/skills/verification-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-mastery", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/xenitV1/claude-code-maestro/tree/main/skills/verification-masteryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install xenitV1/claude-code-maestro verification-mastery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/verification-mastery .agents/skills/verification-mastery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verification-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/verification-mastery into .agents/skills/verification-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-mastery", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install xenitV1/claude-code-maestro verification-mastery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/verification-mastery .cursor/skills/verification-mastery && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verification-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/verification-mastery into .cursor/skills/verification-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-mastery", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/xenitV1/claude-code-maestro.git --path skills/verification-mastery--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install xenitV1/claude-code-maestro verification-mastery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/verification-mastery .gemini/skills/verification-mastery && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verification-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/verification-mastery into .gemini/skills/verification-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-mastery", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install xenitV1/claude-code-maestro verification-masteryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/verification-mastery .github/skills/verification-mastery && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verification-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/verification-mastery into .github/skills/verification-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-mastery", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install xenitV1/claude-code-maestro verification-mastery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/verification-mastery .opencode/skills/verification-mastery && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verification-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/verification-mastery into .opencode/skills/verification-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-mastery", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verification-mastery- GitHub stars
- 229
- Token cost
- ~1.7k tokens
- SKILL.md length
- 537 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Evidence before claims, always. An agent skill from xenitV1/claude-code-maestro.
- Works in 3 steps: Before claiming iteration complete → Quality Gate Check → Completion Signal
- Tasks that involve Verification before completion
- SKILL.md covers 🚨 THE IRON LAW, 🚪 THE GATE FUNCTION, 📋 COMMON CLAIMS AND… and 🚨 RED FLAGS - STOP IMMEDIATELY, plus 8 more sections
- Calls npm, npx and pytest
What it does
Verification Mastery is an agent skill from xenitV1/claude-code-maestro. Evidence before claims, always. No completion claims without fresh verification. The final gate before declaring success.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Verification before completion. The licence is MIT.
When your agent uses it
- Tasks that involve Verification before completion
Example prompts
- “/verification-mastery”
Requirements
- Python 3
- Node.js
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Before claiming iteration complete
- Quality Gate Check
- Completion Signal
What it can do on your machine
Read from SKILL.md and the folder at commit 924315b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmnpxpytestgitruffmypy
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, npx and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verification Mastery loads about 1.7k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 537 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from xenitV1/claude-code-maestro at commit 924315b, republished under its MIT licence (© xenitV1). 537 words, ~1,665 tokens.
Download SKILL.mdSave it as
.claude/skills/verification-mastery/SKILL.md (or your agent's skills folder).- name
- verification-mastery
- description
- Evidence before claims, always. No completion claims without fresh verification. The final gate before declaring success.
<domain_overview>
✅ VERIFICATION MASTERY: EVIDENCE BEFORE CLAIMS
Philosophy: Claiming work is complete without verification is dishonesty, not efficiency. Evidence before claims, always. EVIDENCE INTEGRITY MANDATE (CRITICAL): Never claim a task is complete based on assumption or past memory. You MUST generate fresh evidence (logs, screenshots, test output) for every claim. AI-generated success reports are untrustworthy without proof. Any completion signal sent without accompanying verification artifacts must be rejected as "Hallucinated Success".
🚨 THE IRON LAW
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCEIf you haven't run the verification command in this message, you cannot claim it passes. Violating the letter of this rule is violating the spirit of this rule. </domain_overview> <core_workflow>
🚪 THE GATE FUNCTION
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Skip any step = lying, not verifying</core_workflow> <quality_standards>
📋 COMMON CLAIMS AND REQUIREMENTS
| Claim | Requires | NOT Sufficient |
|---|---|---|
| "Tests pass" | Test command output: 0 failures | Previous run, "should pass" |
| "Linter clean" | Linter output: 0 errors | Partial check, extrapolation |
| "Build succeeds" | Build command: exit 0 | Linter passing, logs look good |
| "Bug fixed" | Test original symptom: passes | Code changed, assumed fixed |
| "Regression test works" | Red-green cycle verified | Test passes once |
| "Agent completed" | VCS diff shows changes | Agent reports "success" |
| "Requirements met" | Line-by-line checklist | Tests passing |
| "No errors" | Command output reviewed | "I think it's fine" |
<red_flags>
🚨 RED FLAGS - STOP IMMEDIATELY
If you catch yourself:
- Using "should", "probably", "seems to"
- Expressing satisfaction before verification ("Great!", "Perfect!", "Done!")
- About to commit/push/PR without verification
- Trusting agent success reports
- Relying on partial verification
- Thinking "just this once"
- Tired and wanting work over
- ANY wording implying success without having run verification ALL of these require: STOP. Run verification. THEN speak.
🚫 RATIONALIZATION PREVENTION
| Excuse | Reality |
|---|---|
| "Should work now" | RUN the verification |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ compiler |
| "Agent said success" | Verify independently |
| "I'm tired" | Exhaustion ≠ excuse |
| "Partial check is enough" | Partial proves nothing |
| "Different words so rule doesn't apply" | Spirit over letter |
| "It worked before" | Run it NOW |
| "Too slow to run again" | Slow verification > fast lies |
| </red_flags> |
KEY PATTERNS
Tests
✅ CORRECT:
[Run: npm test]
[Output: 34/34 passing]
"All 34 tests pass."
❌ WRONG:
"Should pass now"
"Looks correct"
"Tests are green" (without running)Regression Tests (TDD Red-Green)
✅ CORRECT:
1. Write test → Run (MUST PASS initial state or FAIL for right reason)
2. Break the code → Run (MUST FAIL)
3. Fix → Run (MUST PASS)
❌ WRONG:
"I've written a regression test"
(without red-green verification)Build
✅ CORRECT:
[Run: npm run build]
[Output: Compiled successfully]
"Build passes."
❌ WRONG:
"Linter passed, so build should work"
(linter doesn't check compilation)Show full SKILL.md (215 more words)Show less
Requirements
✅ CORRECT:
1. Re-read plan/requirements
2. Create explicit checklist
3. Verify EACH item with evidence
4. Report gaps or confirm completion
❌ WRONG:
"Tests pass, phase complete"
(tests ≠ requirements)Agent Delegation
✅ CORRECT:
1. Agent reports success
2. Check VCS diff (git diff, git status)
3. Verify changes are what was requested
4. Report actual state
❌ WRONG:
Trust agent report without verification</quality_standards> <integration_and_tooling>
🔗 RALPH WIGGUM INTEGRATION
When Ralph Wiggum is active, verification gates are MANDATORY at each iteration:
- Before claiming iteration complete:
- Run all relevant tests
- Run build if applicable
- Run linter if applicable
- Provide evidence in output
- Quality Gate Check:
- Proactive Gate verified?
- Reflection Loop completed?
- Verification Matrix updated?
- Completion Signal:
- Only create
.maestro/ralph.completeAFTER full verification - Include verification evidence in final summary
- Only create
📊 VERIFICATION COMMANDS REFERENCE
JavaScript/TypeScript
# Tests
npm test
npm run test -- --coverage
# Build
npm run build
# Lint
npm run lint
npx eslint . --ext .ts,.tsx
# Type check
npx tsc --noEmitPython
# Tests
pytest
pytest --cov=src
# Lint
ruff check .
flake8 .
# Type check
mypy src/General
# Git status (uncommitted changes)
git status
# Git diff (what changed)
git diff
# Process exit code (last command)
echo $? # Unix
$LASTEXITCODE # PowerShell</integration_and_tooling> <reference_and_audit>
⏱️ WHEN TO APPLY
ALWAYS before:
- ANY variation of success/completion claims
- ANY expression of satisfaction
- ANY positive statement about work state
- Committing, PR creation, task completion
- Moving to next task
- Delegating to agents
- Creating completion signals Rule applies to:
- Exact phrases ("Tests pass")
- Paraphrases ("Everything is green")
- Synonyms ("All good")
- Implications ("Ready for review")
- ANY communication suggesting completion/correctness
💡 WHY THIS MATTERS
From failure analysis:
- "I don't believe you" - trust broken with user
- Undefined functions shipped - would crash in production
- Missing requirements shipped - incomplete features
- Time wasted: false completion → redirect → rework Core principle: Honesty is non-negotiable. Unverified claims are lies.
🏁 THE BOTTOM LINE
No shortcuts for verification. Run the command. Read the output. THEN claim the result. This is non-negotiable.
🔗 RELATED SKILLS
- @tdd-mastery - Verification through failing tests first
- @debug-mastery - Verify fix actually worked
- @clean-code - Quality standards to verify against </reference_and_audit>
© xenitV1, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/verification-mastery of xenitV1/claude-code-maestro.
Open the folder on GitHubat commit 924315b
Compare with similar skills
Verification Mastery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verification Mastery this skillxenitV1/claude-code-maestro | 229 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Loop Change Verifiercobusgreyling/loop-engineering | 11k | 1 repos | ~383 | Automated safety check: Pass | MIT | |
| Verification Skill Maintenancecursor/plugins | 10k | 8 repos | ~1.2k | Automated safety check: Pass | None | |
| Verify and StopJuliusBrussee/caveman | 111k | 1 repos | ~176 | Automated safety check: Pass | Apache-2.0 | |
| Context Modes0xNyk/lacp | 305 | — | ~313 | Automated safety check: Pass | MIT | |
| Verification Before CompletionjnMetaCode/superpowers-zh | 8.3k | — | ~443 | Automated safety check: Pass | MIT |
Similar skills
- Official
Verification Skill Maintenance
cursor/plugins
Audits a project's verification skill and its feature map against the source and the live app, then ships at most one pull request of proven corrections.
Verify and Stop
JuliusBrussee/caveman
Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile…
Context Modes
0xNyk/lacp
Structured work modes for agent sessions. An agent skill from 0xNyk/lacp.
Verification Before Completion
jnMetaCode/superpowers-zh
Chinese-language rule that bars an agent from claiming work is done, fixed or passing until it has run a verification command and read the output.
Iteration Progress Audit
prime-radiant-inc/iterative-development
Checks the quality of behavior evidence after each iteration in three tiers, using two auditor subagents in parallel to review the same work and find gaps.
More from xenitV1/claude-code-maestro
All 13 skills in this repoClean Code
xenitV1/claude-code-maestro
The Foundation Skill. An agent skill from xenitV1/claude-code-maestro.
Ralph Wiggum
xenitV1/claude-code-maestro
Surgical Debugger & Code Optimizer. An agent skill from xenitV1/claude-code-maestro.
Backend Design
xenitV1/claude-code-maestro
Elite Tier Backend standards, including Vertical Slice Architecture, Zero Trust Security, and High-Performance API protocols.
Brainstorming
xenitV1/claude-code-maestro
Design-first methodology. An agent skill from xenitV1/claude-code-maestro.
Browser Extension
xenitV1/claude-code-maestro
Master specialized skill for building 2025/2026-grade browser extensions.
Debug Mastery
xenitV1/claude-code-maestro
Systematic debugging methodology with 4-phase process, root cause tracing, and elite observability standards.
Related
Categories
Questions about Verification Mastery
What does Verification Mastery do?
Evidence before claims, always. An agent skill from xenitV1/claude-code-maestro. Verification Mastery is an agent skill from xenitV1/claude-code-maestro. Evidence before claims, always.
When should I use Verification Mastery?
Verification Mastery fits situations like: tasks that involve Verification before completion.
How do I install Verification Mastery in Claude Code?
Run `npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a claude-code`. Or copy the skill folder (skills/verification-mastery in xenitV1/claude-code-maestro) into .claude/skills/verification-mastery in your project. Claude Code loads it when a task matches its description.
How do I install Verification Mastery in Codex?
Run `npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a codex`. Or copy the skill folder (skills/verification-mastery in xenitV1/claude-code-maestro) into .agents/skills/verification-mastery in your project. Codex loads it when a task matches its description.
Can I use Verification Mastery in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add xenitV1/claude-code-maestro --skill verification-mastery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verification-mastery, .gemini/skills/verification-mastery, .github/skills/verification-mastery and .opencode/skills/verification-mastery in your project.
What does Verification Mastery need to run?
Going by SKILL.md and its folder, Verification Mastery needs the command-line tools its instructions call (npm, npx, pytest, git, ruff and mypy). Our summary lists: Python 3; Node.js.
Does Verification Mastery access the network?
SKILL.md contains no URLs. Its commands use npm, npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Verification Mastery safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verification Mastery use?
Verification Mastery is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verification Mastery use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verification Mastery?
Skills that share tags, products or a category with Verification Mastery: Loop Change Verifier (cobusgreyling/loop-engineering, 11k stars), Verification Skill Maintenance (cursor/plugins, 10k stars), Verify and Stop (JuliusBrussee/caveman, 111k stars) and Context Modes (0xNyk/lacp, 305 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verification Mastery?
xenitV1 (a GitHub user) maintains it in xenitV1/claude-code-maestro, which has 229 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on January 24, 2026.
Source: xenitV1/claude-code-maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.