Refactor
Curated, sanitized export of 21 agent-skill packages for Claude Code and Codex, gated by an automated publication audit (no secrets, no local paths).
npx -y skills add mj-deving/pai-skills --skill RefactorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Lightweight batch refactoring using jscpd, knip, eslint, ast-grep. USE WHEN refactor, scan for duplication, find dead code, unused exports, cleanup session, refactoring pass.
SKILL.md
1.4 KB, as published. Nobody here has run it
Refactor
Lightweight, transparent, stateless batch refactoring. Four CLI tools you own.
/refactor is stretching after exercise — quick, transparent, stateless. Desloppify is an annual physical — comprehensive, scored, persistent.
When to Use
| Say This | Gets You |
|---|---|
/refactor | Full scan→triage→fix→verify cycle |
| "find dead code" / "unused exports" | knip-focused scan |
| "scan for duplication" | jscpd-focused scan |
| "cleanup session" / "refactoring pass" | Full cycle |
When NOT to Use
- Health score / debt audit → use Desloppify
- Review a diff → use /simplify
- Security scan → use /security
Tool Inventory
| Tool | What It Finds | Command |
|---|---|---|
| knip 6.1.1 | Dead code, unused exports, unused deps | npx knip --reporter json |
| jscpd 4.0.8 | Code duplication (cloned blocks) | npx jscpd --min-lines 5 --reporters json --output .refactor/ |
| eslint | Lint violations, deprecation warnings | eslint . --format json |
| ast-grep 0.42.0 | Structural anti-patterns (AST-level) | sg scan --rule <rules-dir> --json |
Workflow
Route to the scan workflow:
→ Workflows/Scan.md — the scan→triage→fix→verify cycle
Gives 0 of the 12 instructions most refactoring skills give
Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06
- run tests after each changein 59 of 521, across 56 files
- write tests before refactoringin 27 of 521, across 24 files
- preserve external behaviorin 26 of 521, across 22 files
- remove dead codein 25 of 521, across 24 files
- make small incremental changesin 20 of 521, across 17 files
- break the implementation into tiny commitsin 18 of 521, across 5 files
- ask the user about alternative optionsin 17 of 521, across 4 files
- create a GitHub issue with the planin 17 of 521, across 4 files
- explore the repository to verify assertionsin 17 of 521, across 4 files
- interview the user about the refactorin 16 of 521, across 3 files
- check the codebase for test coveragein 16 of 521, across 3 files
- refactor one thing at a timein 16 of 521, across 12 files
Said here and by no other author read
- use eslint to find lint violations and deprecation warnings
- use ast-grep to find structural anti-patterns
- run the scan triage fix verify cycle
- use desloppify for health score or debt audits
- use security scan for security
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.