Loading...
Loading...
Found 5 Skills
Review code architecture for maintainability, catch structural issues before they become debtUse when "Reviewing pull requests with structural changes, Planning refactoring work, Evaluating new feature architecture, Assessing technical debt, Before major releases, When code feels "hard to change", architecture, code-review, refactoring, design-patterns, technical-debt, dependencies, maintainability" mentioned.
Audit code architecture for over-engineering and unnecessary abstractions. Use when user asks to "review architecture", "simplify code structure", "reduce over-engineering", "evaluate abstractions", or mentions premature abstraction, interface proliferation, factory patterns, YAGNI, or enterprise-grade complexity.
Review code for architecture: module and layer boundaries, dependency direction, single responsibility, cyclic dependencies, interface stability, and coupling. Cognitive-only atomic skill; output is a findings list.
Analyze the source code of GitHub open-source repositories and generate structured analysis reports. Supports generating reports such as project architecture overview, code quality analysis, core module description, etc., and optional synchronization to Notion.
Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.