verify

Collect evidence from tests and validations to verify code changes.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill verify-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/verify
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill verify-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that a change really works before you claim completion.

Core Features & Use Cases

  • Provide concrete, evidence-based verification for feature changes, fixes, or refactors.
  • Prioritize existing tests, then targeted checks, and document results clearly.
  • Support manual validation when automation cannot cover edge cases.

Quick Start

Run the existing test suite for the change and document the results.

Frequently Asked Questions about verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes before claiming completion?

Verify code changes by running existing tests first, then adding targeted checks or manual validation. This collects concrete evidence proving feature fixes and refactors work before completion.

What is evidence-based validation for software refactoring?

Evidence-based validation runs tests and checks to prove refactored behavior works. It prioritizes existing tests, adds targeted checks, and reports pass or fail results to ensure quality assurance.

How do I run regression tests for feature fixes?

Run regression tests for feature fixes by applying a verification path starting with existing tests, adding targeted checks, and documenting results. This provides concrete evidence that user-facing behavior remains intact.

Can I use manual validation when automated tests cannot cover edge cases?

Yes, you can use manual validation when automation cannot cover edge cases. The verification process supports manual checks to document results and prove that code changes actually work.

What is the best way to prove a code change works without existing tests?

The best way to prove a code change works without existing tests is adding targeted checks and performing manual validation. This collects concrete evidence and clearly reports what passed and failed.

Why does my verification path fail to catch regressions?

Your verification path may fail to catch regressions if it skips existing tests or lacks targeted checks. Clear reporting of what passed and failed is required to prove code changes work.