Measure
Autonomous codebase improvement loop for Claude Code
npx -y skills add benmarte/autoimprove --skill measureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 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
Run the full measurement suite defined in .claude/autoimprove/config.md and report the current codebase quality score (0-100). Use this to check your baseline before running the improve loop, or to spot-check at any time.
SKILL.md
1.2 KB, as published. Nobody here has run it
Measure Skill
Run the project's quality measurement suite and report the composite score.
Steps
-
Read
.claude/autoimprove/config.md. If it doesn't exist, say: "Run /autoimprove:setup first." -
Run each command defined in the config's measurement sections, in order:
- Type check / compile
- Build
- Tests
- Lint
-
Parse results using the error patterns and success patterns defined in the config.
-
Calculate composite score using the weights in the config.
-
Report:
π Codebase Quality Score: XX/100
[Type check label]: X errors β XX/40 pts
[Build label]: β
/β β XX/20 pts
[Test label]: X/X pass β XX/30 pts
[Lint label]: X errors β XX/10 pts
π‘ Lowest area: [label] β [one specific actionable suggestion]
- If any command fails unexpectedly (not just returns errors but actually crashes), report the raw output so the user can debug their tooling.