testing-engineer

Executes a four-layer validation framework on code changes and outputs a structured verification report.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/ponsde/multi-agent-workflow --skill testing-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-engineer
Source: https://github.com/ponsde/multi-agent-workflow/tree/main/skills/tester
Command: npx skills add https://github.com/ponsde/multi-agent-workflow --skill testing-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After code is statically reviewed, teams still need a reliable, repeatable validation phase to ensure changes run correctly in a realistic environment.

Core Features & Use Cases

  • Reads project AI-CONTEXT and change artifacts to build a validation plan.
  • Executes a 4-layer validation framework (function correctness, error handling, integration points, regression) to verify changes.
  • Produces a formal test report with pass/fail status and actionable insights.

Quick Start

Initiate a full validation pass by reading AI-CONTEXT.md and all change artifacts to verify the update runs as expected.

Frequently Asked Questions about testing-engineer

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

FAQPage Schema
How do I automate end-to-end validation of code changes after a static review?

Automate end-to-end validation by reading project AI-CONTEXT and change artifacts to execute a four-layer framework covering function correctness, error handling, integration points, and regression, producing a structured verification report.

What is a four-layer validation framework for runtime code verification?

A four-layer validation framework verifies runtime code correctness by sequentially checking function behavior, error handling, integration points, and regression to ensure reviewed changes run correctly in a realistic environment.

Do I need an AI-CONTEXT file to generate a test coverage report?

You need an AI-CONTEXT.md file and change artifacts to build the validation plan, as the testing process reads these inputs to verify updates and generate a formal test report with actionable pass/fail insights.

When do I need runtime verification instead of just static code review?

Runtime verification is needed when code changes pass static review but require execution in a realistic environment to validate actual behavior, test coverage, and integration points before formal reporting.

What's the best way to check for regression and integration issues after code changes?

The best way to check for regression and integration issues is applying an automated four-layer validation framework that tests function correctness and integration points, outputting a formal report with pass/fail status.

Does end-to-end testing work without writing custom test scripts?

End-to-end testing works without custom scripts by reading existing project specs and AI-CONTEXT to automatically execute the validation framework and output a structured verification report.