Validate code changes by intelligently selecting and running the appropriate test suites. Use this when editing code to verify changes work correctly, run tests, validate functionality, or check for regressions. Automatically discovers affected test suites, selects the minimal set of venvs needed for validation, and handles test execution with Docker services as needed.
SkillScore95Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/21/2026
What it changes
Passed 21 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill95%
Checks it passed that the model alone missed
Runs 1 venv per suite
Limits execution to a single venv
Uses scripts/run-tests --venv e06abee
and 12 more in the full report
13 fixed8 passed either way1 still failing0 broke
Pass-rate lift
+59 pp
Tokens
+131%
Agent turns
0%
Response time
-55%
Model gemini-3.6-flashMeasured 8/21/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
When validating my local changes, `test_view_called_twice` inside the Flask integration tests failed. Can you give me the exact command line invocation to re-run only this specific test function with detailed verbose logging so I can debug the failure?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses scripts/run-tests with arguments passed after --
Missed
Passed
Includes -k test_view_called_twice flag
Passed
Passed
case-03 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md334 linessingle file
Test Suite Validation Skill
This skill helps you efficiently validate code changes by running the appropriate subset of the test suite. It uses scripts/run-tests to intelligently discover affected tests and run only what's necessary for validation.
When to Use This Skill
Use this skill when you have:
Made changes to source code files and want to validate they work
Fixed a bug and want to verify the fix
Added a feature and need test coverage
Modified test infrastructure or configuration
Want to verify changes don't break existing functionality
Key Principles
Always use the run-tests skill when testing code changes - it's optimized for intelligent suite discovery
Never run pytest directly - bypasses the project's test infrastructure (use scripts/run-tests or riot via scripts/ddtest)
Minimal venvs for iteration - run 1-2 venvs initially, expand only if needed
Use --dry-run first - see what would run before executing
Follow official docs - docs/contributing-testing.rst is the source of truth for testing procedures
How This Skill Works
Step 1: Identify Changed Files
First, determine which files were modified:
If you have pending edits, I'll identify the changed files from the current session
I'll look at git status to find staged, unstaged, and untracked changes
You can also specify files explicitly if working on specific changes
Step 2: Discover Available Test Suites
I'll use the scripts/run-tests script to discover what test suites match your changes:
scripts/run-tests --list <edited-files>
This outputs JSON showing:
Available test suites that match your changed files
Systematic framework for evaluating scholarly and research work based on the ScholarEval methodology. This skill should be used when assessing research papers, evaluating literature reviews, scoring research methodologies, analyzing scientific writing quality, or applying structured evaluation criteria to academic work. Provides comprehensive assessment across multiple dimensions including problem formulation, literature review, methodology, data collection, analysis, results interpretation, and