Test an AQE Change
SkillMediaDesign, implement, and run durable tests for Agentic QE code changes. Use when adding tests, reproducing a defect, filling a coverage gap, selecting affected Vitest suites, checking CLI/MCP parity, or verifying a fix in this repository. Do not use for a read-only quality review with no requested edits.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Test an AQE Change skill
What this skill tells your AI
The instructions your AI receives, as published by proffesor-for-testing/agentic-qe in .agents/skills/aqe-test-change/SKILL.md and read by ahel’s review.
- Read
AGENTS.md, the changed code, nearby tests, and relevant public interfaces. - Reproduce a reported defect with the exact scenario before changing code.
- Identify the affected QE specialty from references/test-specialties.md.
- Add tests in this order:
- durable boundary contracts, invariants, or properties;
- integration behavior across affected components;
- focused unit examples needed for the red-green loop.
- Keep tests deterministic. Do not hide failures with retries, skips, weakened assertions, fabricated fixtures, or mocks of the behavior under test.
- Run the narrowest matching Vitest target first. Expand to typecheck, build, agent/skill parity, MCP integration, or full CI checks in proportion to the changed surface.
- For capabilities exposed through both CLI and MCP, verify both paths.
- Report commands, pass/fail counts, limitations, and untested external dependencies.
Never modify or reset .agentic-qe/memory.db. Use a copy for any database test.
Signals
- GitHub stars
- 478
- Forks
- 92
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
aqe-test-change- Source
- github.com/proffesor-for-testing/agentic-qe