test-ops

Classify repository changes to select minimal Taskfile verification entries.

Updated Jun 12, 2025

Search Tags:#testing #frontend #backend #verification #classification #code-change #taskfile

Ready to run

npx skills add https://github.com/saw4405/splat-replay2 --skill test-ops-saw4405

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-ops
Source: https://github.com/saw4405/splat-replay2/tree/main/.codex/skills/test-ops
Command: npx skills add https://github.com/saw4405/splat-replay2 --skill test-ops-saw4405

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps determine the minimal Taskfile entry point needed when changes require a verification path beyond task.exe test, by classifying changes into static, logic, contract, workflow, and performance categories using docs/test_strategy.md as the primary reference.

Core Features & Use Cases

Classification: Distinguishes change types (static, logic, contract, workflow, performance) to select appropriate validation entry points.
Guided Selection: Provides a concise rationale for selecting the entry point and excludes heavy paths when unnecessary.
Documentation-driven: Leverages existing documentation and the Taskfile.yml to map to the correct test/verification entry.

Quick Start

Provide a concise description of the change and the skill will propose the minimal Taskfile verification entry and the rationale.

Frequently Asked Questions about test-ops

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

FAQPage Schema

How do I determine the minimal Taskfile verification entry for a code change?▼

To determine the minimal Taskfile verification entry, classify repository changes into static, logic, contract, workflow, or performance categories using docs/test_strategy.md to select the appropriate validation path beyond basic unit tests.

What is the best way to select a Taskfile check for frontend and backend changes?▼

Selecting a Taskfile check for frontend and backend changes involves classifying the modified entry points against your test strategy documentation to identify the most efficient verification path and exclude unnecessary heavy testing workflows.

When do I need a verification path beyond basic unit tests?▼

You need a verification path beyond basic unit tests when repository changes involve logic, contract, workflow, or performance modifications that require targeted validation entries defined in your Taskfile.yml and test strategy documentation.

How does code change classification map to Taskfile entries?▼

Code change classification maps to Taskfile entries by evaluating frontend and backend modifications against known entry points and test strategy categories, returning the chosen entry, selection rationale, and intentionally omitted items.

Can I use test_strategy.md to skip unnecessary Taskfile verification steps?▼

Yes, using test_strategy.md to classify changes allows you to skip unnecessary Taskfile verification steps by matching change types to minimal validation entries and intentionally excluding heavy paths when they are not required.