Results for “verification-loop”

Structures a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Runs a multi-phase verification pipeline including build, type-check, lint, tests, security scan, and diff review to ensure code quality before creating a PR.

PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.

Verify project behavior anchors — compilation, tests, and interaction checks after autonomous runs. NOT the Claude Code built-in /verify (which runs the app to observe a single change working) — this one walks the CLAUDE.md "Features (Behavior Anchors)" list.

Runs a persistent verification-and-fix loop, executing existing test suites and browser/desktop checks until the requested surface is verified or a real blocker remains.

Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".

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

Use when you want the AI to check back periodically for updates or progress

Iterates through pending development plans in .cursor/plans, implementing tasks, running self-tests, reviewing code, committing locally, and moving completed plans to docs/plans/done.

Scaffolds a per-task verification skill for a repo, including a dev-local launcher, a browser driver, and a verification SOP that spawns a sub-agent to drive the app and produce proof.

Verify that a change really works before you claim completion

PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Enforces a verification gate before any completion claim, requiring fresh command output as evidence.

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

Review a code change for changed behavior that could regress without reliable verification catching it. Use when checking whether a change is adequately verified.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Runs a comprehensive verification pipeline for Django projects including migrations, linting, tests with coverage, security scans, and deployment readiness checks before PRs or releases.

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Autonomous build-ship-verify loop that ends with code committed, deployed, and confirmed live. Triggers on: "$ownership", "execute X with ownership", "build this overnight", or any request for an autonomous product loop with no human checkpoints until production is verified. NOT for: one-off tasks, quick fixes, or supervised dev work (use devprocess for those).

Verify work before committing, pushing, or requesting review

Runs a QA validation cycle followed by bugfix until all criteria pass clean, with automated verification and re-validation.

面向ECC的以证据为先的实时消息工作流。当用户想要阅读短信或私信、恢复最近的一次性验证码、在回复前检查对话线程，或证明实际检查了哪个消息来源时使用。

[OMX] Strict autonomous loop: $deep-interview -> $ralplan -> $ultragoal (+ $team if needed) -> $code-review -> $ultraqa

Runs a two-wave validation pipeline (deterministic checks then rule-based checks) before every git commit, writing a sentinel file that a pre-commit hook enforces. Includes optional quick mode (first wave only) and a fix loop with up to three iterations.

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Prove code works by running it, not just checking it exists. Verification through execution rather than inspection. Use after writing or modifying code to ensure it actually functions correctly.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Use when profiling, diagnosing, or improving Three.js or WebGL game performance without regressing gameplay—frame-time drops, CPU/GPU pressure, draw calls, texture/geometry budgets, animation loops, adaptive quality, mobile performance, and browser performance verification.

Apply one logical code change with mandatory impact mapping, git snapshot, verification, and automatic revert on failure. Load when the user asks for a safe edit, verified change, one change at a time with rollback, or codespine-style edit loop. Also triggers on "safe change", "edit with verification", "don't break the build", "revert if tests fail", or any non-trivial code edit where blast radius matters. Always runs dependency-mapping first. Pairs with incremental-implementation for multi-slice work; this skill is one atomic verify cycle per invocation.