Skip to content
cccskills
FreePublished on GitHub

verify

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

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

See how to install

Files included (1)

  • SKILL.md4.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

/supergraph:verify

Requires healthy index_status for CBM_PROJECT (see references/codebase-memory-contract.md); then codebase-memory-mcp detect_changes, trace_path, recipes cycles/hubs/bridges/test-gaps. Block on degraded/new cycle/unapproved hub/missing tests.

Fresh verification gate before completion claims.

Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

When to Use

Before saying/implying: done, fixed, passing, clean, ready, complete, works, verified, successful. Also: before marking Status: completed, committing, PR'ing, accepting agent reports, moving to next phase.

Usage

/supergraph:verify | tests | lint | build | plan auth-login task 2 | claim "login fixed"

Evidence Mapping

ClaimRequired fresh evidence
Tests pass$TEST_CMD exits 0, zero failures
Lint clean$LINT_CMD exits 0, zero errors
Build succeeds$BUILD_CMD exits 0
Bug fixedOriginal failing symptom/test now passes
Regression coveredRED failed before fix, GREEN passes after
TDD completeRED failure valid, GREEN passes, refactor verified
Task completedAcceptance criteria met + verification commands pass
Agent completedDiff inspected + independent tests/lint
Review passedReviewer + graph review + tests/lint pass
Ready to mergeTests + lint + build + review PASS

Steps

0. Announce

"✅ /supergraph:verify — verifying [claim] with fresh evidence..."

1. Identify Claim

Map claim to required proofs from evidence mapping.

2. Select Plan Context (if applicable)

0 plans → skip | 1 → use | >1 → ask | plan <slug> → match.

3. Get Commands

Read from plan ## Environment Context or .supergraph-env (set by /supergraph:scan). Missing → STOP, run scan first. No command can prove claim → STOP: "Required check is unknown."

3b. Serena sweep (optional): See serena/SKILL.md:Setup — get_diagnostics_for_file per touched file; STOP on type errors before test suite. Skip if SERENA_ACTIVE=false or unavailable.

4. Run Fresh Verification (NOW — no reuse of old output unless freshness guard passes)

For agent output: git diff --stat && git diff --name-only. Then run relevant tests/lint/build locally. Freshness guard (dedup suite, preserves Iron Law): Reuse of immediately prior evidence is allowed only if HEAD_SHA unchanged and git diff --name-only HEAD unchanged and last PASS timestamp <120s ago (same commit). Otherwise must rerun $TEST_CMD/$LINT_CMD fresh NOW. Guard respects CBM_INDEXED_AT TTL from /supergraph:scan but never skips verification before merge/PR — if HEAD_SHA changed, reuse is invalid.

5. Read Output

Check: exit code, failure count, error count, warnings. Don't confuse lint ≠ build, targeted ≠ suite.

6. Report Evidence

Pass:

## Verification Evidence
- Claim: [claim] | Command: `[command]` → exit 0 → PASS
- Evidence: [output summary] | Timestamp: [now]

Fail:

## Verification Failed
- Claim: [claim] | Command: `[command]` → exit [N] → FAIL
- Failure: [summary] | Next: /supergraph:fix

Cannot verify → say so explicitly. No completion language.

7. Update Plan Status

Only after evidence passes: in_progress → completed. If failed → keep status or mark stuck if retries exhausted.

For user-facing confirmation: Announce task/plan completion in the user's language. If plan context exists, show: "Task N completed — [user-facing summary]"

8. Report

✅ /supergraph:verify complete
- Claim: [claim] | Evidence: [command] → PASS|FAIL
- Next: [recommendation]

Anti-Patterns — Block These

  • "should work" / "seems fixed" / "probably passes" / "looks good"
  • Trusting agent reports without independent check
  • Stale command output | No acceptance criteria check
  • Commit/PR without fresh tests+lint+build+review evidence
  • Hiding skipped checks behind positive wording

Evidence Rules

Evidence before claims, always. Fresh only — old runs don't count. Read output before reporting. No positive language without proof. Agent output requires independent verification.

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

Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.

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

datit309/supergraph21Updated Oct 18, 2026

Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.

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

datit309/supergraph21Updated Oct 18, 2026

Autonomous human-like browser control and professional QA/QC testing. Powered by agent-browser (Rust native CDP, zero Playwright) with ISTQB test matrix generation, automated testcase execution, console/network error tracing, and defect reporting.

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

datit309/supergraph21Updated Oct 18, 2026

Persistent token-compression mode (~75% reduction) — now always-on by default. Strips filler while keeping code exact.

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

datit309/supergraph21Updated Oct 18, 2026

Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

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

datit309/supergraph21Updated Oct 18, 2026

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

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

datit309/supergraph21Updated Oct 18, 2026

See all skills by datit309

Report a problem with this skill