yeachan-heo/verifyv1.0

verify

Verify that a change really works before you claim completion

v1.0LATEST

NewUpdated Sep 9, 2026

Verify

Use this skill when the user wants confidence that a feature, fix, or refactor actually works.

Goal

Turn vague “it should work” claims into concrete evidence.

Workflow

Identify the exact behavior that must be proven.
Prefer existing tests first.
If coverage is missing, run the narrowest direct verification commands available.
If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence.
Report only what was actually verified.

Verification order

Existing tests
Typecheck / build
Narrow direct command checks
Manual or interactive validation

Rules

Do not say a change is complete without evidence.
If a check fails, include the failure clearly.
If no realistic verification path exists, say that explicitly instead of bluffing.
Prefer concise evidence summaries over noisy logs.

Output

What was verified
Which commands/tests were run
What passed
What failed or remains unverified

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

72/100

Grade

Good

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

Safety

Quality

Clarity

Completeness

Summary

This skill guides an agent to verify that code changes actually work by following a structured validation workflow. It prioritizes existing tests first, then typechecks/builds, narrow direct commands, and manual validation as fallbacks. The agent reports concrete evidence of what passed or failed rather than making unsupported claims.

Detected Capabilities

run shell commandsexecute teststypecheck/build verificationread test outputgather manual validation evidence

Trigger Keywords

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

verify change workstest before completionconfirm build succeedsvalidate fixproof of behavior

Use Cases

Verify a bug fix works before closing an issue
Validate a feature implementation before merging
Confirm a refactor didn't break existing behavior
Gather evidence that a build succeeds in the current state
Document what manual testing steps were performed and their results

Quality Notes

Clear, pragmatic workflow with explicit ordering (prefer tests → typecheck → narrow commands → manual)
Strong emphasis on evidence-based validation and honest reporting (rules explicitly forbid claiming completion without proof)
No explicit edge cases documented (what if tests don't exist? what if build is expensive?)
Minimal technical specifics — agent is given principles but limited actionable detail on *how* to verify different project types
No guidance on scope boundaries — does this skill apply to all verification needs or only certain contexts?

Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 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/verify in your dev environment — a Developer account adds skills to your library and syncs them via the SkillRepo CLI.

Start a Developer trial