SkillRepo
Sign InSign Up
Catalog
Yeachan-Heo/maintain-verification-skill

Yeachan-Heo

maintain-verification-skill

Re-sync the project's verification skill when its commands drift — re-run each recorded command, update expectations and the feature map to what is true now, record the verdict actually earned.

v1.0LATEST
NewUpdated Nov 8, 2026

Maintain Verification Skill

A verification skill that names dead commands is worse than none: it fails loudly on trivia and passes quietly on what matters. This skill re-syncs the project's verify skill to the repo's current reality.

When to use

  • verification errors on a command that no longer exists or was renamed
  • a new surface (package, app, e2e suite) has no check recorded
  • after a toolchain or CI migration

Workflow

  1. Audit the recorded skill: list every command and manual check it names; for each, does the command still exist and still mean the same thing (flags, scripts, config)?
  2. Re-run, don't re-read: execute each surviving command and compare the observed outcome to the recorded expectation. A command whose passing shape changed gets its expectation rewritten, with the new evidence.
  3. Find uncovered surface: what does the repo build/check now that the feature map does not mention? Add the check by running it, or record the gap as uncovered — the map stays honest.
  4. Update the skill and feature map in place: same file, corrected commands, corrected coverage table, dated revision line at the top.
  5. Record the resync through the ledger's locked writer — appendLedgerEntry and defaultLedgerPath from the installed package's dist/features/verification-ledger/index.js (babysit's ledger step demonstrates the exact invocation); never append raw rows to .omc/state/verification-ledger.tsv — the writer owns header creation, locking, and cell sanitization. The verdict is the one the rerun actually earned — unit-test-verified when the test suite ran, live-ui-verified for a live-UI flow, type-check-only when only build/lint/typecheck commands were rerun — and those commands as evidence. Never claim a test ran that did not.

Rules

  • The rerun is the resync; nothing is marked current without execution.
  • Coverage that shrank is reported out loud, not silently dropped from the map.
  • If the project's verification has outgrown the single skill shape (multi- package, per-app checks), say so and split per surface rather than fattening one file.
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

85

Quality

84

Clarity

81

Completeness

76

Summary

This skill guides agents to re-sync a project's verification skill by re-running recorded verification commands, comparing outcomes to expectations, and updating the skill and feature map to reflect current reality. It establishes a workflow for auditing command validity, executing surviving checks, discovering new verification gaps, and recording resync verdicts through a controlled ledger writer.

Detected Capabilities

read verification skill fileexecute shell commands (verification suite)read project configurationupdate skill documentationwrite verification ledger entriesfilesystem reads

Trigger Keywords

Phrases that agents use to match this skill to user intent.

sync verification commandsupdate verification skillverify command driftresync after migrationverification coverage gapsverification command audit

Risk Signals

INFO

Ledger writer library invocation (appendLedgerEntry, defaultLedgerPath from installed package)

Workflow step 5, instructions for recording resync
INFO

Guidance to avoid raw file appends and use controlled writer for ledger updates

Workflow step 5, explicit rules
INFO

Instructions reference external package (babysit) as demonstration source

Workflow step 5

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.com

Use Cases

  • Re-sync verification after toolchain migration
  • Update verification skill when commands are renamed or removed
  • Add coverage for new build surfaces or test suites
  • Audit existing verification commands for current validity
  • Record verification resync with accurate verdicts and evidence
  • Reconcile verification skill with multi-package project changes

Quality Notes

  • Clear, goal-oriented workflow with specific steps (audit → re-run → find gaps → update → record)
  • Explicit safety guardrails: emphasis on re-running commands (not re-reading), using controlled ledger writer, and never claiming tests ran without execution
  • Strong emphasis on honesty and accuracy: coverage shrinkage is reported loudly, verdicts must match actual evidence, no silent drops
  • Good contextual trigger examples (When to use section)
  • Practical references to ledger infrastructure and specific package exports make guidance concrete and actionable
  • Rules section reinforces core principles (rerun is resync, honesty about coverage, multi-package refactoring)
  • Well-scoped to verification skill maintenance only — not a general testing or CI/CD skill
Model: claude-haiku-4-5-20251001Analyzed: Nov 8, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use Yeachan-Heo/maintain-verification-skill in your dev environment

Start a Developer trial

Command Palette

Search for a command to run...