refactor-with-tests
Skill1 starsChanged 6 months agoMITView on GitHub
Use when splitting files, improving architecture, reducing duplication, changing internals, or preserving behavior through focused tests during refactors.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms.txtllms.txt
- ai-app-security-reviewSkill
- codeaudit-orchestratorSkill
- codeauditSkill
- docs-claims-evidence-reviewSkill
- enterprise-code-qualitySkill
- github-issue-pr-workflowSkill
- nextjs-security-reviewSkill
- official-docs-groundingSkill
- python-backend-qualitySkill
- python-mcp-server-qualitySkill
- skill-supply-chain-auditorSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Add or locate tests that cover the behavior.
- Distinctive: line 15
Run relevant tests and typecheck.
- Distinctive: line 16
Update docs only when behavior, architecture, or setup changes.
- Distinctive: line 21
Do not combine unrelated refactors.
- Distinctive: line 22
Do not rename public APIs without an explicit migration reason.
- Distinctive: line 23
Do not weaken validation, auth, error handling, or observability to simplify code.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Refactor With Tests
Workflow
- Identify the exact behavior to preserve.
- Add or locate tests that cover the behavior.
- Make the smallest useful refactor.
- Run relevant tests and typecheck.
- Update docs only when behavior, architecture, or setup changes.
- Summarize changed files and validation.
Guardrails
- Do not combine unrelated refactors.
- Do not rename public APIs without an explicit migration reason.
- Do not weaken validation, auth, error handling, or observability to simplify code.
- Preserve user changes in a dirty worktree.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.