Write tests for the code you just changed
For developers who know they should write tests but would rather Claude did it well: add tests for exactly the code you changed, in the style your project already uses. Finds each changed file's tests, flags code with none and tests that did not change with the code, detects your framework (Vitest, Jest, Mocha, node:test, pytest, Go, RSpec), then writes focused tests for the new behavior and edge cases, runs them, and shows each one can fail. Never weakens a test to make it pass.
- Activity
- New: be the first to try it
Will this work for me?
- Effort
- Needs about 10 minutes of setupOur guess from what the kit says it needs.
- Works in
- Claude Code, claude.ai and the desktop app
- You need
GitHub account: setup steps
- What it is
- This kit works with your own GitHub account.
- Where to get it
- Sign in to GitHub, or make a free account if it offers one. Go to GitHub
Safety label
- Who made it
How this works
- It is a skill: written instructions Claude reads when your request matches what the skill is for. You do not call it by name; just ask for the task.
- While it works, it reads and changes files in the places it lists, nowhere else.
- It runs these commands on your computer: node scripts/untested-changes.mjs, git diff, git status, git merge-base, npm test, pnpm test, yarn test, npx vitest run, npx jest, python3 -m pytest, go test.
- Nothing runs until you choose to use it, and you can remove it any time.
What it can access
What this kit says it will touch, the same list you see before you add it. These are its Permissions: What a kit is allowed to touch on your computer or accounts, such as reading a folder or using the internet. You see them before you add it.. In Claude Code they become rules, so Claude stops anything not on the list.
Command
Runs the command: node scripts/untested-changes.mjs (with any arguments, without asking)
Command
Runs the command: git diff (with any arguments, without asking)