Validate code changes with automated unit and integration tests and generate a test.md report.
npx skills add https://github.com/SimpleEve/eo-skills --skill eo-test
Please help me install this Agent Skill. Skill: eo-test Source: https://github.com/SimpleEve/eo-skills/tree/main/eo-test Command: npx skills add https://github.com/SimpleEve/eo-skills --skill eo-test
Provides a disciplined, repeatable way to write, run, and document tests for implemented changes so that feature acceptance is verified without touching production business code or silently patching failures.
Run eo-test for module my-module and change 001-add-feature to write and run tests against eo-doc/dev/my-module/changes/001-add-feature/change.md and produce eo-doc/dev/my-module/changes/001-add-feature/test.md.
High-intent search queries and answers about installing and using this skill.
To generate and run automated tests, target repository modules containing a change.md document and implemented code. The system writes independent unit and integration tests, executes project test commands, and produces a structured test.md report with execution evidence.
Test reporting works by enforcing strict safety guardrails that prohibit modifying non-test business code. It collects test outputs, exit codes, and execution logs, then records any discovered failures in a standardized test.md report within the change directory rather than patching them inline.
Yes, you can validate acceptance criteria by deriving scenario, unit, and integration tests directly from the change.md document. The system executes these tests against the implemented code and outputs a structured test.md report containing summary metrics and failure analysis.
The best way to document test failures is to generate a standardized test.md report in the change directory. This report includes summary metrics, independent execution logs, failure analysis, and reproduction evidence without altering the original business code.
Automated change validation records bugs instead of fixing them to maintain disciplined, repeatable testing without silently patching failures. It enforces a strict prohibition on modifying non-test business code, ensuring production logic remains untouched while failures are documented in the test report.
Yes, you need the directory structure eo-doc/dev/<module-name>/changes/<change-id>/ containing a change.md file and implemented code. The system applies tests to this specific structure and outputs the resulting test.md report directly into the same change directory.
SimpleEveReview implemented code against spec.md and change.md, generating review.md reports.
tomgunWrite and run unit, integration, and acceptance tests for code changes.
anotbCompare two policy versions and generate a detailed change log.
samChang72Automate unit, integration, and component tests with Vitest and Testing Library.
