Identify structural weaknesses and generate architectural improvement proposals in Markdown.
npx skills add https://github.com/max4c/skills --skill improve-codebase-max4c
Please help me install this Agent Skill. Skill: improve-codebase Source: https://github.com/max4c/skills/tree/main/skills/improve-codebase Command: npx skills add https://github.com/max4c/skills --skill improve-codebase-max4c
Architectural review that produces proposals, not commits. Read the codebase, identify structural improvement opportunities — shallow modules that should be deepened, leaky abstractions, misplaced complexity — and presents them with tradeoffs for the user to decide. The output is a Markdown decision document.
Run the improve-codebase skill against your codebase to generate a 2-5 proposal architecture document.
High-intent search queries and answers about installing and using this skill.
To get architectural improvement proposals for a codebase with shallow modules, run an automated review that identifies structural weaknesses and generates a Markdown document with 2-5 actionable improvements, rationale, and tradeoffs.
The best way to review leaky abstractions without automatic refactoring is to generate decision documents that analyze misplaced complexity and present architectural proposals with tradeoffs, leaving the final implementation decision to the user.
A four-persona analysis stress-tests software design proposals by applying Contrarian, Simplifier, Architect, and Hacker perspectives to evaluate structural weaknesses, ensuring architectural improvements are robust before presenting them in a Markdown document.
Yes, you can use architectural review tools to estimate the effort needed for modular design changes by generating proposals that include rough effort estimates alongside rationale and tradeoffs for each identified structural improvement.
You need an architectural review instead of a standard code review when your codebase exhibits structural issues like leaky abstractions or misplaced complexity, and you require a high-level proposal document rather than direct code commits.
Your codebase analysis outputs a Markdown decision document instead of code changes because the process is designed to produce architectural proposals with tradeoffs, saving the review to docs/architecture-reviews/ for user evaluation rather than executing refactors.
jankneumannAnalyze codebase complexity, coupling, duplication, and import issues to generate markdown and JSON reports.
captainflasmrAnalyze codebases for quality issues and implement refactoring changes.
ezrelafidelynnAnalyze and visualize codebase dependencies and relationships using Python graph libraries.
MudraMartinAnalyze .NET codebases for shallow modules and propose architectural refactors.
