Test Follow-up
After each code change, proposes exactly which tests to add (what, where, which cases) and lets you decide
Free
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsTest Follow-up
Example session with this skill installed
I've finished updating the calculateDiscount function in src/utils/pricing.ts to handle the new seasonal tiers. What's next?
- Read your context and instructions
- Compiled the test follow-up
Work on the change is complete. Shall I add tests?
- Proposal: Add
pricing.spec.tsinsrc/utils/for the change insrc/utils/pricing.ts - Cases (4): standard discount tier / peak season tier / negative input handling / zero-value transactions
- Reply "yes" to proceed, "no" to skip, or "later" to leave a follow-up TODO only
Next steps
- Reply yes to generate the Vitest suite based on your existing utility patterns.
- Reply later if you want to push the logic now but keep a
TODOin the file. - Reply no if this is a spike or exploratory change.
Connects securely to your tools. The creator never sees your data.
About this skill
What it does
Agents tend to either skip tests entirely or write them unasked. Test Follow-up sits in between: right after your agent changes production code, and before it says "done", it asks you once whether to add tests, with a concrete proposal.
- Analyzes the change to find the behavior and edge cases worth verifying.
- Follows your project's conventions: reads existing tests first to match the framework (Vitest, Jest, Playwright, ...), location, and file naming. It never introduces new tooling.
- Picks the right test type: unit tests for pure functions, component tests, E2E for page flows, one regression test for a bug fix. For refactors it says plainly when the existing passing tests may be enough.
- Short proposal, then your call: what to test, where, and which cases, in 1–3 lines. Yes means it writes and runs the tests. No means it stops and does not ask again. Later means it leaves a one-line TODO.
When it stays quiet
Docs, config, or static content changes; throwaway spike code; or when you already said "skip tests".
Who it's for
Developers who want tests to stay their decision, without having to remember to ask every time.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 5 days ago
- Free to download with an account