Verify code changes by running tests and documenting evidence.
npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill verify-robinnorberg
Please help me install this Agent Skill. Skill: verify Source: https://github.com/RobinNorberg/oh-my-copilot/tree/main/skills/verify Command: npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill verify-robinnorberg
Verify that a change truly works by producing concrete evidence that it behaves as intended.
Describe the change you made and run the verification workflow to generate a concrete evidence report.
High-intent search queries and answers about installing and using this skill.
To verify a code change works with concrete evidence, you describe the change to generate a detailed verification report. This report documents which commands were run, the observable outcomes, and a clear pass or fail verdict.
The best way to validate behavior after refactoring code is to prefer running existing tests and documenting any coverage gaps. When automation is insufficient, outline manual validation steps and capture observable outcomes to prove the refactor works.
You document test coverage gaps during validation by selecting the appropriate verification path for your change. This path prioritizes existing tests and explicitly records coverage gaps to minimize additional work while producing a concise verification report.
Yes, you can validate fixes when automated tests are insufficient by following outlined manual validation steps. This process captures observable outcomes and produces a verification report detailing what was manually validated.
A verification report for quality assurance should include what was verified, which commands were run, and the resulting outcomes. It provides a clear verdict to prove that features, fixes, or refactors truly work as intended.
timbuchingerEnforce writing failing tests before implementing minimal code to pass.
mvillmowGenerate HTML and terminal coverage reports for Python pytest runs.
Pryma-TechVerify code changes by running tests and reporting pass/fail evidence.
koasis89Analyze code repositories read-only with confidence levels and evidence boundaries.
