Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/dinhanhthi/coding-friend --skill cf-verificationLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Affichage de SKILL.md
Answer questions about Coding Friend — skills, agents, hooks, CLI, config, memory, hosts, parameters. Auto-invoke when the user asks about Coding Friend capabilities, available skills, how to use a skill, what skills / agents / commands / hooks exist, flags or parameters, how it works, or how to configure it — e.g. "what skills are available?", "how does coding friend work?", "what can you do?", "list all skills", "what agents exist?", "how do I use cf-plan?", "what is cf-tdd?", "what flags does X have?", "what hooks exist?", "how do I get started?", "coding friend features/setup", "does X require the CLI?", "what works without coding-friend-cli?", "is the CLI required?". Do NOT auto-invoke for general coding questions unrelated to Coding Friend itself.
Answer questions about Coding Friend — skills, agents, hooks, CLI, config, memory, hosts, parameters. Auto-invoke when the user asks about Coding Friend capabilities, available skills, how to use a skill, what skills / agents / commands / hooks exist, flags or parameters, how it works, or how to configure it — e.g. "what skills are available?", "how does coding friend work?", "what can you do?", "list all skills", "what agents exist?", "how do I use cf-plan?", "what is cf-tdd?", "what flags does X have?", "what hooks exist?", "how do I get started?", "coding friend features/setup", "does X require the CLI?", "what works without coding-friend-cli?", "is the CLI required?". Do NOT auto-invoke for general coding questions unrelated to Coding Friend itself.
Answer questions about Coding Friend — skills, agents, hooks, CLI, config, memory, hosts, parameters. Auto-invoke when the user asks about Coding Friend capabilities, available skills, how to use a skill, what skills / agents / commands / hooks exist, flags or parameters, how it works, or how to configure it — e.g. "what skills are available?", "how does coding friend work?", "what can you do?", "list all skills", "what agents exist?", "how do I use cf-plan?", "what is cf-tdd?", "what flags does X have?", "what hooks exist?", "how do I get started?", "coding friend features/setup", "does X require the CLI?", "what works without coding-friend-cli?", "is the CLI required?". Do NOT auto-invoke for general coding questions unrelated to Coding Friend itself.
| 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" |