Menü
Verify before claiming work is complete
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Dispatch code review to a subagent. Use when the user wants code reviewed — e.g. "review this", "review my changes", "check the code", "look over this", "code review", "any issues with this?", "is this code ok?", "review before merge", "review the diff", "what do you think of these changes?". Also triggers on requests to review specific files, commits, or branches.
Dispatch code review to a subagent. Use when the user wants code reviewed — e.g. "review this", "review my changes", "check the code", "look over this", "code review", "any issues with this?", "is this code ok?", "review before merge", "review the diff", "what do you think of these changes?". Also triggers on requests to review specific files, commits, or branches.
Save a concise checkpoint of the current conversation's context — goal, decisions, breaking changes, next steps — into a file for resuming later in a DIFFERENT conversation. Use when the user says things like "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (condenses context within the SAME conversation), this produces a durable, resumable snapshot for a fresh conversation. Unlike $cf-remember (durable project-wide facts/conventions for AI recall across all future work), this is a transient per-conversation resume artifact. Does NOT auto-invoke — slash-only.
Brainstorm and write an implementation plan. Use when the user wants to plan, build, create, or implement something — e.g. "let's build", "let's create", "I want to create", "create for me", "build for me", "add feature", "implement", "make a", "set up", "I need a", "can you build", "help me build", "how should we implement", "design a solution", "architect", "scaffold", "plan out", "figure out how to", "what's the best way to build". Also triggers on task descriptions that imply multi-step implementation work requiring upfront planning.
In-depth research on a topic with web search and structured output. Use when the user wants deep research before building — e.g. "research this", "look into this library", "investigate how X works", "compare these options", "what are the best practices for", "deep dive into", "study this technology", "analyze this repo", "explore the ecosystem around". Also triggers when the user needs to understand a technology, library, or architecture pattern in depth before making decisions.
Save a concise checkpoint of the current conversation's context — goal, decisions, breaking changes, next steps — into a file for resuming later in a DIFFERENT conversation. Use when the user says things like "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (condenses context within the SAME conversation), this produces a durable, resumable snapshot for a fresh conversation. Unlike /cf-remember (durable project-wide facts/conventions for AI recall across all future work), this is a transient per-conversation resume artifact. Does NOT auto-invoke — slash-only.
| name | cf-verification |
| description | Verify before claiming work is complete |
| created | "2026-02-17T00:00:00.000Z" |
| updated | "2026-07-04T00:00:00.000Z" |
CLI Requirement: NONE — Works without
coding-friend-cli. See CLI requirements for the full matrix.
Custom guide — auto-loaded below (if the raw command shows instead of its output, run it yourself):
bash "${PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-verification
If output is not empty, integrate returned sections: ## Before → before first step, ## Rules → apply throughout, ## After → after final step.
No completion claims without fresh verification evidence.
Claiming work is complete without verification is dishonesty, not efficiency.
Auto-invoke this skill after tasks that produce or modify code (implementation, bug fixes, refactoring).
Do NOT auto-invoke after analysis-only skills that don't change code:
$cf-review — code review is analysis, not implementation$cf-plan — planning doesn't produce code$cf-ask — Q&A doesn't produce code$cf-research — research doesn't produce codeBefore claiming ANY task is done:
| Good Evidence | Bad Evidence |
|---|---|
| Test output showing all pass | "I believe the tests pass" |
| Build output with exit code 0 | "The build should work" |
| Actual command output | "I ran the tests" (without output) |
| Screenshot of UI change | "The UI looks correct" |
git diff showing the change | "I made the change" |