evidence-proof

Execute npm test and generate confidence reports for code changes.

1|Updated Mar 7, 2026

Search Tags:#automation #testing #quality assurance #code verification #evidence gathering #confidence score

Ready to run

npx skills add https://github.com/jimmymalhan/codereview-pilot --skill evidence-proof

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evidence-proof
Source: https://github.com/jimmymalhan/codereview-pilot/tree/main/.claude/skills/evidence-proof
Command: npx skills add https://github.com/jimmymalhan/codereview-pilot --skill evidence-proof

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that code changes are rigorously verified through automated testing and manual checks, providing objective evidence of their correctness and preventing the deployment of untested or partially implemented features.

Core Features & Use Cases

Automated Testing: Executes npm test and captures detailed output including pass/fail counts, coverage percentages, and duration.
Evidence Gathering: Collects proof from test runs, manual verification of critical workflows, and code review diffs.
Confidence Scoring: Assigns a numerical confidence score based on a defined rubric, documenting unknowns and residual risks.
Use Case: After fixing a bug, run this Skill to automatically execute all relevant tests, verify the fix manually on a local server, and generate a confidence report detailing the test results, any remaining risks, and a rollback plan.

Quick Start

Run the evidence-proof skill to verify recent code changes and generate a confidence report.

Frequently Asked Questions about evidence-proof

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

FAQPage Schema

How do I verify code changes with evidence before deployment?▼

You can verify code changes with evidence by automating test execution, capturing pass/fail outputs, manually checking critical workflows, and documenting any residual risks to ensure correctness before deployment.

What is a confidence score in code verification?▼

A confidence score in code verification is a numerical rating assigned based on a defined rubric, evaluating test results and manual checks to objectively quantify the reliability of recent code changes.

How do I gather proof that a bug fix is correct?▼

To gather proof that a bug fix is correct, execute automated tests like npm test, verify the fix manually on a local server, and generate a confidence report detailing test outputs, remaining risks, and a rollback plan.

Does automated evidence gathering capture test coverage and duration?▼

Automated evidence gathering captures detailed test outputs including pass/fail counts, coverage percentages, and duration, providing concrete proof that all code changes are backed by systematic testing.

When should I document unknowns and residual risks in testing?▼

You should document unknowns and residual risks during the confidence scoring phase, ensuring that any incomplete verifications or potential edge cases are explicitly recorded before considering a code change complete.

Can I generate a rollback plan after verifying code changes?▼

Generating a rollback plan is a core use case after verifying code changes, where the skill details test results, remaining risks, and rollback procedures to prevent the deployment of untested features.