verify-feature
De la autor
Verify that a feature as built actually matches what was asked for — catching requirements that were quietly dropped, built differently than specified, or built without being asked for. Use this whenever you are partway through or wrapping up a feature and about to call it done, and whenever the user says "does this match the PRD/spec", "did we drift", "is this what I asked for", "check this against the requirements", "verify the feature", "did you build everything", or reviews work before a commit or PR. Also reach for it unprompted at the midpoint of any multi-step feature, before more code gets stacked on a wrong foundation. This answers "did we build the right thing" — it is not the code-quality gate (lint / typecheck / tests) and not `security-review`.
Instalare
npx skills add arcasilesgroup/ai-engineering --skill verify-feature -a claude-code
Se instalează în .claude/skills/verify-feature/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 82
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- completion-verificationcbrock84/headcountVerifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.Inginerie★ 2.1K
- verification-before-completionGanyuanRan/AegisUse when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.Inginerie★ 1.4K
- gate-checktranhieutt/software_development_departmentValidates a software product, service, or feature against readiness gates before advancing to the next delivery phase. Use when planning a phase transition or when the user mentions gate check, phase review, or readiness validation.Planificare★ 74
- build-checkarcasilesgroup/ai-engineeringRun the project's objective quality gates — typecheck, lint, tests, and a production build, whatever this project actually uses — then diagnose any failure down to the file and root cause. Use before committing, opening a PR, or declaring work done, and whenever asked whether the code compiles, typechecks, lints, tests, or builds.Testare★ 61
- ai-verifyarcasilesgroup/ai-engineeringUse when work has to be verified — "verify the feature", "did we build what was asked", "review this diff", "is it ready to commit" — by choosing the right verification tier (standalone, embedded, or chain) and producing verdicts with evidence, not impressions. Not for milestone-declared security audits — use /ai-security. Not for diagnosing a failure — use /ai-debug.Securitate★ 61
- dev:validateraphaelchristi/harness-evolverUse when the user wants to validate the plugin, check integrity, verify cross-references, or before a release. Also use when the user says 'validate', 'check plugin', or 'verify'.Altele★ 57
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te