testing

Design, execute, and report tests that verify implemented changes against requirements and policies.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026⬇️3downloads

When & Why to Use This Skill

This Claude skill automates the end-to-end software testing lifecycle, from designing test cases based on requirements to executing suites and reporting defects. It ensures high code quality by verifying that implemented changes align with technical specifications and organizational policies while proactively identifying coverage gaps.

Use Cases

  • Automated Regression Testing: Executing relevant test suites after code changes to ensure existing functionality remains intact and stable.
  • Policy Compliance Verification: Validating that new implementations strictly adhere to internal 'testing_policy', security guardrails, and commit rules.
  • Defect Discovery and Reporting: Automatically capturing execution logs and routing detailed defect reports to the development team for faster debugging.
  • Requirement Validation: Designing specific test cases that map directly to functional requirements to ensure the software behaves as expected.
nametesting
descriptionDesign, execute, and report tests that verify implemented changes against requirements and policies.

Purpose

Deliver test updates and results that validate the implemented changes and surface defects.

Inputs

  • Implemented changes and expected behavior
  • Test strategy from plan/architecture
  • Applicable policies (testing_policy, guardrails, commit_pr_rules) and environment details

Steps

  1. Load changes, requirements, and testing policies.
  2. Identify coverage goals; design or update tests accordingly.
  3. Execute relevant test suites; record commands and results.
  4. Report defects to the reviewing flow; summarize coverage and gaps.

Outputs

  • Test cases or updates, executed results with commands, and defects routed to review.

Failure modes

  • Skipping required tests or policies
  • Incomplete coverage for changed behavior
  • Altering product logic beyond test scaffolding