Analyzed Aug 17, 2026
juliusbrussee/caveman
safe-refactor
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.
Installation
npx skills add juliusbrussee/caveman --skill safe-refactor
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
11.9K installsPre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
1.5K installsConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…
1.5K installsAzure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…
1.5K installsPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
1.4K installsCreate new skills, modify and improve existing skills, and measure skill performance. Use when …
927 installsSecurity audits
Partner security reviews for this skill.
Analyzed Aug 17, 2026
Analyzed Aug 17, 2026
0 alerts
Also in this package
Other skills from juliusbrussee/caveman · top by installs.
npx skills add juliusbrussee/caveman
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md705 B -
docs
SUMMARY.md177 B
History
- First seen on skills.sh
- First recorded snapshot · 39,900 installs
SKILL.md
Safe refactor
Define behavior-preservation boundary and establish verification before structural edits.
- Keep feature changes outside refactor.
- Move one ownership boundary at a time.
- Preserve public interfaces, failure behavior, ordering, and compatibility unless explicitly scoped.
- Keep intermediate states buildable and testable.
- Avoid dependency or configuration growth without correctness need.
Run same proof after change. Stop when behavior matches and requested structure is achieved.