Skip to content
cccskills
FreePublished on GitHub

verify

Check whether a feature, fix, or refactor actually works using existing tests, build checks, direct commands, or manual validation. Get a concise account of the evidence, including what passed, what failed, and what remains unverified.

OriginalShow the original description

Verify that a change really works before you claim completion

See how to install

Good for

  • Checking that a bug fix works
  • Verifying a newly added feature
  • Checking behavior after a refactor
  • Reporting verification evidence and remaining gaps

Files included (1)

  • SKILL.md1.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

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

Verification order

  1. Existing tests
  2. Typecheck / build
  3. Narrow direct command checks
  4. 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

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

Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.

  • Clarifying instructions in CLAUDE.md
  • Making specifications and tickets actionable
  • Adding completion criteria to skill procedures
Yeachan-Heo/oh-my-claudecode40.2KUpdated Oct 21, 2026

ai-slop-cleaner

FreeSummary

Simplify bloated AI-generated code by removing dead code, duplicated logic, and unnecessary layers while checking that existing behavior stays intact. Use a limited cleanup scope, verify changes with relevant checks, or request a review without edits.

  • Removing duplicate logic and unused code
  • Simplifying unnecessary wrappers without changing behavior
  • Cleaning up only a specified set of changed files
Yeachan-Heo/oh-my-claudecode40.2KUpdated Oct 21, 2026

Review module relationships and change history to identify structural improvements in a codebase. Receive ranked candidates with file references, suggested changes, and risks, plus a recommendation for where to start, without modifying code.

  • Reviewing architecture after a batch of changes
  • Investigating changes that touch too many files
  • Prioritizing structural improvements
Yeachan-Heo/oh-my-claudecode40.2KUpdated Oct 21, 2026

ask

FreeSummary

Send questions, review requests, or implementation tasks to a supported local AI command-line tool through one shared command. The wrapper handles provider-specific options and saves the result as a Markdown file for later reference.

  • Requesting a security review of a patch
  • Seeking UX suggestions for a user flow
  • Drafting an implementation plan for an issue
Yeachan-Heo/oh-my-claudecode40.2KUpdated Oct 21, 2026

ask-navigator

FreeSummary

Turn an unclear idea into linked decision tickets on a repository’s issue tracker. Work through one decision per session, record outcomes and dependencies, and prepare a brief defining the objective, scope, and exclusions for delivery.

  • Clarifying the destination of an early idea
  • Mapping decisions and their dependencies
  • Resuming unresolved decisions across sessions
Yeachan-Heo/oh-my-claudecode40.2KUpdated Oct 21, 2026

autopilot

FreeSummary

Turn a short product idea into working code through requirements analysis, technical planning, implementation, testing, and review. It coordinates agents across these stages, fixes detected problems, and reports assumptions that still need a human decision.

  • Building a product from a short idea
  • Creating a bookstore inventory API
  • Developing a habit-tracking command-line tool
Yeachan-Heo/oh-my-claudecode40.2KUpdated Oct 21, 2026

See all skills by Yeachan-Heo

Report a problem with this skill