agent-tester

Analyze code diffs and coverage to generate and execute scoped tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/TrevorPLam/agency --skill agent-tester-trevorplam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-tester
Source: https://github.com/TrevorPLam/agency/tree/main/.windsurf/skills/agent-tester
Command: npx skills add https://github.com/TrevorPLam/agency --skill agent-tester-trevorplam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and runs tests to ensure code changes do not introduce regressions and maintain adequate test coverage throughout the codebase.

Core Features & Use Cases

  • Triggered testing: Runs tests whenever code behavior changes, coverage thresholds drop, or test-infra workflows execute.
  • Multi-level scope: Generates and executes unit, component, integration, and end-to-end tests for changed areas.
  • Test authoring & reporting: Assists writing tests, runs them, and reports coverage and results with actionable feedback.

Quick Start

Trigger the tester agent on the latest commit to generate and execute tests.

Frequently Asked Questions about agent-tester

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

FAQPage Schema
How do I automate test generation for code changes?

Automating test generation for code changes involves analyzing diffs and coverage to scope tests across unit, component, integration, and end-to-end levels, then writing and executing tests that fail on insufficient coverage.

How does test automation validate requirements from code diffs?

Test automation validates requirements by reading code diffs, identifying affected files, organizing a test plan, and generating tests that execute against changed areas to ensure behavior remains stable and coverage meets thresholds.

Can I use this to write unit, component, and integration tests?

Yes, you can use this to write unit, component, integration, and end-to-end tests. It scopes tests across these levels based on the changed files and executes them to report coverage and actionable results.

Do I need Vitest to run automated tests on my commits?

Vitest is supported as a keyword for test automation, but the core task focuses on analyzing diffs and generating tests that fail on insufficient coverage, adaptable to your testing-library and CI-CD workflows.

What is the best way to maintain test coverage after modifying code?

The best way to maintain test coverage is to trigger automated testing on code changes, which scopes tests to the modified areas, writes new tests, and fails execution if coverage thresholds drop below acceptable limits.

Why does test execution fail when coverage drops?

Test execution fails when coverage drops because the automation setup explicitly checks coverage thresholds after executing tests, ensuring code changes do not introduce regressions and maintain adequate coverage throughout the codebase.