Навыки: Разработка

Run verification checklist before marking work complete. Use when verifying task completion, checking deployment success...

Verifies Puck changes: landing bar, builds, stale DLLs, flaky tests, GPU/heavy leases, coverage, source-scan or regex la...

Verify before claiming completion. No claims without fresh verification evidence. Use before marking work done.

Verify Godot work is complete and error-free before claiming done or committing — use before every git commit.

Use before claiming work is complete, fixed or passing, or before commit/PR: run verification, evidence first.

Use when about to claim work is complete, fixed, verified, or passing, before committing or creating PRs - requires runn...

Use before claiming work is complete, fixed, or passing, and before committing or opening a PR - run the actual verifica...

Use when about to report a task, story, build, or Definition of Done condition as complete, or before checking off any i...

Requires running verification commands and reading their actual output before any claim that work is complete, fixed, or...

Gate every completion claim behind executed evidence. Use before saying "done", "fixed", "works", "passing", "delivered"...

Runs verification commands and confirms output before success claims. Use before claiming work done or committing or PRs...

Use when about to claim work is complete, fixed, or passing, or to express satisfaction, or before committing/pushing/op...

Use before declaring any task complete, claiming code works, or asserting changes are correct in scala-ts. Requires fres...

Defense-in-depth verification before declaring any task complete.

Confirms fixes are effective before marking complete

Requires fresh, actually-run evidence before any claim that a task is complete. Use when about to tell the user a task,...

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verifi...

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verifi...

Use when about to claim work is complete, fixed, passing, or findings are confirmed - requires running verification and...

Run verification commands and confirm output before claiming success. Use when about to claim work is complete, fixed, o...

Internal verification gate for delivery-flow. Use before delivery-flow claims work is complete, fixed, or passing; do no...

Assess nontrivial completion evidence.

在声明任务完成、修复成功或测试通过前，必须先跑一遍验证命令并确认输出；提交、开 PR 前同样适用。证据先于结论，永远如此。

Use when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documen...

Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements...

Run a five-phase verification of work in Travel-Tool (build and type check, lint, backend tests, a diff secrets grep, an...

Claude Code 会话的全面验证系统。

Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security gr...

This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes",...

Runs the full quality gate loop (build, types, lint, tests, secrets scan, diff review) for Node, Python, and Flutter pro...

A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before cla...

A comprehensive verification system for Codex sessions.

Runs the full DevSkyy gate battery (pytest, ruff, phpcs/phpstan, verify:theme, .min rebuild, live curl, eyes-on) and rep...

Verification planning for non-trivial coding work. Use before implementing a feature, bug fix, refactor, cross-system ch...

verifier. Use when you need help with verifier.

Run an explicit user-requested criteria-driven verification loop. Use when the user asks to define success criteria, clo...

Use when a plan's tasks are landed and its branch needs the gate before a pull request, the scripted checks, the branch...

Run the backend verification loop after Kotlin/Spring code changes — Kotlin style + unit tests via `gradlew verify`, plu...

Drive EZR's actual surfaces to confirm a change works — the program runner, the browser interface, and the tool CLIs. Us...

Fresh verification gate before claiming done, fixed, passing, ready, or before commit/PR. Evidence before claims, always...

Run the full ChefFlow verification protocol - spec audit, build integrity, production parity, and Playwright pressure te...

Adversarial verification of implementation work. Spawns a read-only subagent that runs builds, tests, linters, and probe...

Verify code changes work by running them. Proves through execution, not just inspection.

Verify a change is done by running lint, the Prettier check, the test suites, and a production build. Use after finishin...

Verify code or product claims after changes using fresh, risk-matched evidence. Use before saying a bug is fixed, tests...

Run kajet-turbo locally against a temp DB and a fake embedding endpoint, then drive the REST surface (login, notes, jobs...

Exercise a change end to end in the running application (hit the route, run the command, click through the page) and rep...

Build, relaunch, and observe the Claudence menu bar app to verify a change end-to-end.