About code-upgrade
code-upgrade is a skill for AI coding tools that reviews code structure and quality through focused audits. It explains findings in plain language for non-engineers and proposes changes rather than applying them automatically.
Key features
- 01Combined audits with Normal and Deep modes
- 02Architecture explanations and review
- 03Plan checklist before approval
- 04Checks for errors and silent fallbacks
- 05Unused and duplicated code detection
- 06Idempotency review for retry behavior
Use cases
- 01Reviewing an application before planning changes
- 02Checking a proposed plan before approval
- 03Finding hidden failures and silent fallbacks
- 04Identifying unused or duplicated code
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ robinebers/ skills --skill code-upgradeAfter installing, type/code-upgradein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
architecture-audit.mdbloat-audit.mdduplicate-audit.mdfail-fast-audit.mdmaster-audit.mdplan-checklist.mdretry-audit.mdDetails
From the project READMEThe Code Upgrade
AI coding tools that wrap engineering-principles into skills for normal people.
The tools
- The Master Audit: Run architecture + duplicate + fail-fast + bloat + retry and return one short executive plan. Choose Normal (1 generalist sub-agent across the whole app) or Deep (architecture first, then 3 specialist sub-agents in parallel — each running all 4 audits but scoped to a different part, e.g. frontend / backend / other). Costs more, says more.
- The Architecture Audit: Explain the app, then let user grill it.
- The Plan Checklist: Use before approval a plan to verify and simplify it.
- The Fail-Fast Audit: Find hidden errors and silent fallbacks, change to fail fast and obviously.
- The Bloat Audit: Find unused code, explain it, and remove if not needed.
- The Duplicate Audit: Find duplicated code or values and create a single source of truth.
- The Retry Audit: Find spots in the code that have bad idempotency.
CRTICIAL RULES
- Always treat the user as non-technical, non-engineer.
- Plain English. 10-year-old understands.
- Teach the concept briefly, don't dodge it.
- Propose, don't auto-apply.
- Run multiple async subagents aggressively to increase hits.
Future Skill Ideas
- (none yet)
Comments
Markdown supported