completion-verifier
About
The completion-verifier skill automatically validates implementation work by running acceptance tests against the codebase. It parses test specifications, executes the appropriate test framework, and reports detailed pass/fail results. When tests fail, it identifies the problematic phase and triggers a retry loop to fix the implementation.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/completion-verifierCopy and paste this command in Claude Code to install this skill
Documentation
Completion Verifier Skill
When to Use
- After each implementation phase
- Before marking task as complete
- When retry loop is triggered
Inputs
- context.md path (contains Acceptance Tests section)
- Test framework (from PROJECT.md: jest/vitest/playwright)
Procedure
- Parse Acceptance Tests section from context.md
- Extract test IDs and file paths
- Run tests:
npm test -- --testPathPattern="{test files}" - Parse results (PASS/FAIL per test)
- Update context.md status column
- Return completion status
Output
completionStatus:
total: 5
passed: 4
failed: 1
allPassed: false
failedTests:
- id: T2
type: Unit # or Integration
file: ErrorHandler.test.tsx
error: "Expected error message not shown"
failedPhase: "Phase 1" # Determines where to retry
recommendation: "Fix ErrorHandler.tsx, then re-run Phase 1"
Retry Logic
When allPassed: false:
-
Identify failed phase based on test type:
- Unit FAIL → Phase 1 (Mock implementation)
- Integration FAIL → Phase 2 (API integration)
-
Return to failed phase (NOT test writing):
- Pass
failedTestsinfo to implementation-agent - Implementation-agent fixes code only (no test rewrite)
- Pass
-
Retry limits:
- Max 2 retries per phase
- After 2 failures → Ask user for intervention
Skip Conditions
- No test framework configured → Skip with warning
- No Acceptance Tests in context.md → Skip
- Skip Conditions from testing.md apply (legacy, prototype, etc.)
Tool Call Example
# Run specific tests
npm test -- --testPathPattern="batch.test|ErrorHandler.test"
# Check coverage (optional)
npm test -- --coverage --testPathPattern="..."
GitHub Repository
Related Skills
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
sglang
MetaSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
evaluating-llms-harness
TestingThis Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.
langchain
MetaLangChain is a framework for building LLM applications using agents, chains, and RAG pipelines. It supports multiple LLM providers, offers 500+ integrations, and includes features like tool calling and memory management. Use it for rapid prototyping and deploying production systems like chatbots, autonomous agents, and question-answering services.
