
from dotfiles8
Audit code architecture and maintainability to find unnecessary complexity, misplaced abstractions, duplication, and high-impact refactoring opportunities.
Design Audit reviews codebases for architectural and structural problems that make working with the code expensive or risky. The skill focuses on maintainability: premature or missing abstractions, duplication, unclear module boundaries, circular dependencies, and other structural smells. It walks representative call sites and modules rather than guessing from filenames, and it prioritizes findings by maintenance impact and confidence. When invoked with an --accept flag it can apply high-confidence, behavior-preserving refactors and run available tests before committing.
Use Design Audit when you need a focused, higher-level review of a codebase or a specific path to surface refactoring opportunities and concrete repair plans. Good for onboarding, pre-release reviews, or when a code area is becoming brittle. Do not use it for bug fixes, security audits, or style-only issues. If you want runnable quick fixes, include --accept.
Compatible with code-focused agents that can read repositories and run tests (e.g., Codex/Copilot-style or code-execution-capable assistants).
Design audit skill for reviewing code architecture and maintainability. No bundled scripts — pure prompt-based skill with detailed instructions on identifying abstraction problems, complexity, structural issues, and duplication. Well-structured SKILL.md with clear workflow, specific findings taxonomy, and explicit scoping (what not to flag). Useful for code review but not unique in this space.
Clean, instruction-only skill with no scripts or security concerns. The --accept auto-commit behavior is well-documented and gated behind an explicit flag, so not a real risk. SkilL.md is thorough and well-organized.