القائمة
Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | verification-gate |
| description | Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion |
Part of the hidden validation layer. User never sees this running, but it prevents false "Done!" claims.
Core principle: Never show success to user without evidence.
/mvp:deploy/mvp:add featureBEFORE showing success to user:
[ ] Tests pass (run full suite, not partial)
[ ] Build succeeds (no compilation errors)
[ ] No TypeScript/linting errors
[ ] Feature actually works (manual smoke test)
[ ] Security checks pass (from security-check skill)
[ ] Code review clean (from code-review-auto skill)
ALL must pass. ANY failure = fix silently, don't show error to user.
What user sees:
Adding login feature...
✅ Done! Check your preview.
What happens behind the scenes:
1. Generate login code
2. Run tests → 2 failures
3. Fix failures automatically
4. Run tests → pass
5. Run build → pass
6. Security check → pass
7. Code review → 1 minor issue
8. Fix issue automatically
9. All gates pass → show "Done!"
If gate fails and can auto-fix:
If gate fails and cannot auto-fix:
Run all checks programmatically:
python scripts/verify.py --path /project/path --language rust
python scripts/verify.py --path /project/path --json # JSON output
The script auto-detects language and runs appropriate checks.
Called by:
/mvp:build - Before showing preview/mvp:add - Before confirming feature added/mvp:deploy - Before deploymentUses:
User paid for "vibe coding" - they describe what they want, we handle how.
Showing them test failures or build errors breaks the magic.
Fix it. Don't explain it.
Learn Claude Code in 5 hands-on lessons. From basics to building applications. Use when: user wants to learn Claude Code, asks "how do I...", or is new. Triggers: "learn", "teach me", "how does this work", "I'm new", "course".
Help and navigation for Claude Code Course. Use when: user asks about the course, lessons, or progress. Triggers: "help", "course help", "what lessons", "my progress".
Assess Claude Code knowledge and route to appropriate learning level. Use when: user wants to learn Claude Code, asks for guidance, or says "teach me". Triggers: "learn Claude Code", "teach me", "I'm new", "where do I start", "beginner".
Describe your idea, get a deployed product. All Craft Coder skills + brainstorm, validation, marketing. Use when: user wants to build something from an idea, prototype, or MVP. Triggers: "build app", "create website", "make MVP", "I have an idea", "хочу приложение", "создать сайт", "сделать MVP".
Manages course progress tracking in ~/.claude-course/progress.json. Use when: loading, saving, or displaying course progress. Internal skill - used by /ccc:course commands.
Lesson content for Claude Code Course. Use when: loading lesson content. Internal skill - contains lesson files.