QualityPython

Verification Before Completion

by GanyuanRan

Verification Before Completion is a Quality skill for Claude Code, published by GanyuanRan in Aegis.

1.1K stars50 forkson GanyuanRan/AegisAdded 2026/08/21+2% in starsRepository updated 2026/08/19
agent-skillsai-agentsai-codingarchitecture-driven-developmentawsome-coding-pluginbaseline-firstclaude-codecodexcoding-agentsdivedsh-pluginevidence-drivenfirst-principlesopencodesoftware-architecturespec-driven-developmentspec-kit
Install in seconds
Install Verification Before Completion
Copy Verification Before Completion into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/GanyuanRan/Aegis/tree/main/skills/verification-before-completion ~/.claude/skills/verification-before-completion

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/GanyuanRan/Aegis.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/verification-before-completion/SKILL.md in GanyuanRan/Aegis
Installs to
~/.claude/skills/verification-before-completion
Collection
One of 22 skills cataloged from this repository
Category
Quality1354 skills

What Verification Before Completion does

Verification Before Completion requires a fresh falsifying check and explicit evidence before claiming work is complete, fixed, or ready to hand off. Use it when preparing to commit, merge, publish, release, or otherwise declare success.

Verification Before Completion is cataloged under Quality on DirSkills. Verification Before Completion comes from a repository tagged agent-skills, ai-agents, ai-coding, architecture-driven-development and awsome-coding-plugin.

Documentation

README

Execute

Before any success claim, classify destructive permission needs, choose and run a fresh falsifying check, read its complete result/scope, then select L0/L1/L2. If evidence is partial, stale, failing, or narrower than the claim, downgrade; never claim complete first and verify later.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Verification Before Completion

  • What else does GanyuanRan publish alongside Verification Before Completion?

    Verification Before Completion is one of 22 skills that DirSkills catalogs from GanyuanRan/Aegis, the repository it ships in. Its siblings there include Aegis Goal Framing, Anti-Entropy Governance and Brainstorming. Each one is a separate skill with its own page in this directory, installs the same way Verification Before Completion does, and is maintained by GanyuanRan in that same repository. The rest of the collection is listed on the GanyuanRan/Aegis page.

  • How does Verification Before Completion compare to other Quality skills?

    Verification Before Completion ranks #791 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Verification Before Completion against them. Open each page to compare what they document and how they install.

More from GanyuanRan/Aegis

Verification Before Completion is one of 22 skills cataloged on DirSkills from GanyuanRan/Aegis.

See all 22 skills
🎯
1w ago

Aegis Goal Framing

Aegis Goal Framing creates a thin goal frame before execution when a user sets an Aegis goal or asks for scope, success evidence, or stop conditions. It is used to define boundaries before routing into the next workflow.
AI Engineering
1.1K50
🧭
1w ago

Anti-Entropy Governance

Anti-Entropy Governance helps decide when to delete old code paths, collapse duplicate owners, or remove fallbacks safely. It also guards schema, persistence, and source-of-truth changes that need explicit confirmation.
AI Engineering
1.1K50
🧠
1w ago

Brainstorming

Brainstorming helps turn ambiguous or high-complexity ideas into clearer designs by asking focused questions, comparing approaches, and shaping a spec before implementation. Use it for new features, architecture, contracts, or plan pressure-tests.
AI Engineering
1.1K50
🔍
1w ago

Code Review Reception

Code Review Reception helps you evaluate code review feedback before making changes. Use it when comments are unclear, risky, disputed, or may conflict with the codebase or prior decisions.
Quality
1.1K50
✍️
1w ago

Communicating Concisely

Communicating Concisely shortens responses when the user asks for caveman mode, fewer tokens, or brief answers. It drops filler and keeps technical details exact until turned off.
Writing
1.1K50
🤖
1w ago

Dispatching Parallel Agents

Dispatching Parallel Agents delegates unrelated tasks to separate agents with isolated context. Use it when 2+ independent problems can be worked in parallel; otherwise handle them inline or with a planned subagent workflow.
AI Engineering
1.1K50