skills.rest
Hyeonjun0527
Hyeonjun0527COMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify

Collect test, build, and manual check evidence to verify change behavior.

1|Updated Apr 6, 2026
Search Tags:#documentation#validation#build#evidence#verify#reproducible#tests
One-click install
npx skills add https://github.com/Hyeonjun0527/yeon --skill verify-hyeonjun0527
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/Hyeonjun0527/yeon/tree/main/.codex/skills/verify
Command: npx skills add https://github.com/Hyeonjun0527/yeon --skill verify-hyeonjun0527

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying that a feature, fix, or refactor actually works by producing tangible evidence rather than vague claims.

Core Features & Use Cases

  • Evidence-driven validation: Collect and present concrete results from tests, builds, or manual checks.
  • Clear reporting: Output what was verified, the commands run, and verification outcomes.
  • Use Case: When you ship a change, use this to confirm the behavior with reproducible proof.

Quick Start

Run the existing tests and document the verification results to prove the change actually works.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify that my code changes work with concrete evidence?▼

To verify code changes, run existing tests and document the verification results. Collect tangible proof from test suites, builds, and type checks to confirm behavior rather than relying on vague claims.

What is evidence-driven validation for software development?▼

Evidence-driven validation is the process of proving feature work or bug fixes by collecting and presenting concrete results from tests, builds, and manual checks to expose any gaps and confirm success.

How do I document reproducible results for a bug fix?▼

Document reproducible results by clearly reporting the verification outcomes, the exact commands run, and the specific behavior proven. This establishes reproducible proof that your fix actually works.

Does verifying a refactor require explicit evidence from type checks?▼

Yes, verifying a refactor requires explicit evidence from type checks, tests, and documented outcomes. This deterministic validation confirms success and exposes any gaps across your development workflow.

What is the best way to prove a feature behaves correctly before shipping?▼

The best way to prove a feature behaves correctly is to identify the exact behavior to prove and collect verifiable evidence from manual checks, builds, and tests to produce reproducible proof.

When do I need to collect verifiable evidence during a development workflow?▼

You need to collect verifiable evidence whenever shipping a change for a feature, fix, or refactor. It confirms the behavior with deterministic validation and reproducible results rather than assumptions.

Related Skills

Explore More Software Engineering Skills→
spiralhousespiralhouse
5

baseline-check

Run RuboCop and RSpec checks against previous baselines to detect regressions.

Official
Intermediate
Matt-Aurora-VenturesMatt-Aurora-Ventures
58

verification-before-completion

Enforce a verification gate with fresh test results before claiming completion.

Community
Intermediate
billydeeii136billydeeii136

health

Compute a weighted 0-10 codebase health score and track trends over time.

Community
Intermediate
GainInsightDevGainInsightDev

af-test-coverage

Analyze Jest coverage reports to identify untested code paths.

Official
Intermediate