Skip to content
cccskills
FreePublished on GitHub

verify

AI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success. Use when completing any task, fixing a bug, finishing a phase, running tests, building, deploying, or making any "it works" claim.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.2 KB
  • agents/openai.yaml300 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Verify

Prove it works before saying it works.

Hard Rules

  • Do not claim completion without fresh terminal evidence from this session.
  • Forbidden words in completion claims: "should", "probably", "seems to", "likely", "I believe", "I think it works". These signal unverified assertions.
  • Cached, remembered, or previous-session output is not evidence. Run it again.

Gate Function

Every completion claim must pass all 5 steps in order:

  1. Identify — What command proves this claim? If multiple commands are needed, run the gate once per command.
  2. Run — Execute the full command now. No partial runs, no skipping.
  3. Read — Read complete output. Check exit code. Count pass/fail.
  4. Confirm — Does the output prove the exact claim?
  5. Report — State the result, cite command, exit code, and key output.

If any step fails, stop. Fix the issue and restart from step 1.

If no verification command exists (e.g., no test suite), tell the user and ask them how to verify before claiming done.

Verification Patterns

ClaimRequired EvidenceNot Sufficient
Tests passTest output: 0 failures, exit 0Previous run, "should pass now"
Build succeedsBuild output: exit 0Linter passing, partial build
Bug is fixedReproduce symptom → now passes"Changed code, should be fixed"
Linter cleanLinter output: 0 errorsSingle file check
Phase completeEach criterion verified individually"Tests pass, so done"
Feature worksE2E test or manual walkthroughUnit tests alone

Regression Verification

For bug fixes, a single pass is not enough:

  1. Write a test covering the bug.
  2. Run → must pass (fix in place).
  3. Revert the fix.
  4. Run → must fail (proves test catches the bug).
  5. Restore the fix.
  6. Run → must pass.

If step 4 passes, the test is wrong. Rewrite it.

Red Flags and Rationalizations

RationalizationWhy It's WrongDo Instead
"This change is trivial"Trivial changes break things constantlyRun the check
"I ran it earlier"Code changed since thenRun it again now
"The test is flaky"Flaky ≠ ignorableFix the flake first
"It compiles, so it works"Compilation ≠ correctnessRun the tests
"The CI will catch it"CI is a safety net, not a substituteVerify locally first
"The agent said it's done"Agent claims need verification tooCheck diff and run tests

Memory Integration

After a failed verification, store the failure pattern: npx ai-devkit@latest memory store --title "<failure pattern>" --content "<what failed and how to avoid>" --tags "verify,failure-pattern"

Task Tracing

If a task name is known and tracing is usable, record task evidence after the verification report per task. If tracing was not probed, run the real read probe first. If probe or evidence recording fails, report the failed task command and continue verification; never block verification on optional task logging.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send. Use when an agent needs to find another active agent, read its recent context, send it information, or request information back.

The English summary is being prepared. Showing the original description.

codeaholicguy/ai-devkit1.7KUpdated Oct 18, 2026

AI DevKit · Manage running AI agents with ai-devkit agent commands. Use when an agent needs to identify itself, list agents, start workers, inspect agent detail, assign work, group agents, resume sessions, stop agents, or delegate work to other agents.

The English summary is being prepared. Showing the original description.

codeaholicguy/ai-devkit1.7KUpdated Oct 18, 2026

AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions.

The English summary is being prepared. Showing the original description.

codeaholicguy/ai-devkit1.7KUpdated Oct 18, 2026

AI DevKit · Check local AI DevKit readiness and run setup only when status shows onboarding or harness integration gaps.

The English summary is being prepared. Showing the original description.

codeaholicguy/ai-devkit1.7KUpdated Oct 18, 2026

AI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow choices, name something, plan content angles, explore strategy, evaluate product ideas, technical approaches, experiments, or decisions.

The English summary is being prepared. Showing the original description.

codeaholicguy/ai-devkit1.7KUpdated Oct 18, 2026

AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.

The English summary is being prepared. Showing the original description.

codeaholicguy/ai-devkit1.7KUpdated Oct 18, 2026

See all skills by codeaholicguy

Report a problem with this skill