Verification Before Completion
Use when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documentation updated.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill verification-before-completiongit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/verification-before-completion ~/.claude/skills/verification-before-completionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Verification Before Completion ## Core Principle Before declaring ANY work "complete" or "done", verify EVERYTHING works. This is the final gate before handoff. ## When to Use This Skill - After completing `code-review` skill - User asks "is it done?" - **BEFORE EVERY COMMIT** (mandatory) - Before creating pull request - Before closing an issue - Before marking a feature as complete ## The Iron Laws ### 1. NEVER DECLARE WORK COMPLETE WITHOUT FULL VERIFICATION Reasons: - Ensures nothing was forgotten - Confirms everything actually works - Validates against original requirements - Prevents "one more thing" scenarios - Professional quality gate ### 2. NEVER COMMIT WITHOUT VERIFICATION **This skill is MANDATORY before ANY git commit.** If you find yourself typing `git commit` without having completed this verification checklist, **STOP**. ❌ **FORBIDDEN:** ```bash # Making changes vim src/file.js git add . git commit -m "fix stuff" # ← WRONG! No verification! ``` ✅ **REQUIRED:** ```bash # Making changes vim src/file.js # MANDATORY: Run verification-before-completion skill # Complete ALL checklist items # Only after FULL verification passes: git add . git commit -m "fix(api): handle null values in user profile" ``` **Authority**: Professional teams NEVER commit without verification. Unverified commits cause: - 🐛 Bugs in production - 💥 Broken builds - 😡 Wasted team time - 💸 Lost customer trust ### 3. FRONTEND + BACKEND = FULL TEST SUITE
Details
- Skill name
verification-before-completion- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/verification-before-completion/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Verification Before Completion skill do?
Use when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documentation updated.
How do I install the Verification Before Completion skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Verification Before Completion popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Voice E2E Test
8Freddy-CHEN-ux/00_claude_skills
Comprehensive E2E test of voice call pipeline - place call, verify auth flow, monitor transcripts/scores, verify report. Use when user says "test voice e2e", "run voice test", or "full voice test".
Unit Testing Principles
5vnovakovits/claude-skills
Apply Vladimir Khorikov's unit testing framework from "Unit Testing Principles, Practices, and Patterns" (Manning, 2020). Covers the four pillars (protection against regressions, resistance to refactoring, fast feedback, maintainability) and their unavoidable trade-offs, the three styles of unit testing (output-based, state-based, communication-based), observable behavior vs implementation details as the line that separates good and bad tests, mocks vs stubs with strict verification rules, the managed vs unmanaged dependency distinction (the most useful heuristic for deciding what to mock), wh
Xunit Test Patterns
5vnovakovits/claude-skills
Apply Gerard Meszaros's "xUnit Test Patterns — Refactoring Test Code" (2007) — the canonical catalogue of test-automation patterns, the test-double taxonomy (Dummy, Stub, Spy, Mock, Fake), test smells, fixture strategies, and result-verification patterns. Use when writing or refactoring test code; diagnosing brittle, slow, erratic, or obscure tests; choosing and naming a test double; designing fixtures (fresh vs shared, Object Mother, Test Data Builder, setup styles); structuring the four-phase test; deciding where to draw the test boundary (subcutaneous / layer / round-trip); faking out-of-pr
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.