verify-change

Document validation evidence and commands in docs/test-report.md.

13|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Thrimbda/legion-mind --skill verify-change-thrimbda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-change
Source: https://github.com/Thrimbda/legion-mind/tree/main/skills/verify-change
Command: npx skills add https://github.com/Thrimbda/legion-mind --skill verify-change-thrimbda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validation of implemented changes should produce credible, traceable evidence rather than relying on assumptions or further large-scale rewrites. This skill guides selecting the most efficient validation path and recording outcomes.

Core Features & Use Cases

  • Evidence-first validation: prioritizes producing verifiable results from existing changes.
  • Decision support: helps determine targeted versus full validation strategies and documentation approach.
  • Documentation output: results are compiled into docs/test-report.md with commands, outcomes, and rationale.

Quick Start

Run the validation workflow to generate a test-report for your existing changes.

Frequently Asked Questions about verify-change

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

FAQPage Schema
How do I generate validation evidence for code changes instead of assumptions?

To generate validation evidence, you can apply a workflow that identifies and records credible results from existing code changes, compiling verifiable outcomes rather than relying on assumptions or rewrites.

When should I choose targeted validation versus full validation for my engineering changes?

Choosing targeted versus full validation depends on your implemented changes; this skill provides decision support to help determine the most efficient validation strategy and documents the rationale for your chosen approach.

How do I document executed test commands and outcomes in a test report?

You document executed test commands and outcomes by running the validation workflow, which automatically compiles the executed commands, their results, and the justification into a `docs/test-report.md` file.

What is evidence-first validation in software engineering?

Evidence-first validation is a process that prioritizes producing verifiable, traceable results from existing code changes to ensure software quality, avoiding reliance on unverified assumptions during the validation phase.

Does this validation approach require any specific testing frameworks or dependencies?

No specific testing frameworks or dependencies are required to start; the validation process operates on your existing code changes to produce the necessary documentation and verifiable outcomes.