complexity
Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.
Browse published AI skills maintained by bchapuis. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
7Repository stars across indexed skills
7Repository forks
0Average repository stars per indexed skill
1Repository stars may repeat across skills from the same repository.
Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.
Core software design principles from 'A Philosophy of Software Design'. Use when asking about decomposition, deep modules, information hiding, complexity management, or John Ousterhout's design principles.
Reviews API designs for simplicity and error handling. Use when designing APIs, evaluating interface complexity, or eliminating error conditions.
Reviews code comments for quality. Use when reviewing documentation or evaluating if code is self-documenting.
Reviews modules for depth vs shallowness. Use when designing APIs, reviewing class interfaces, or evaluating abstraction value.
This skill should be used when the user asks to "write specifications", "specify an abstraction", "create contract tests", "property-based testing", "design by contract", "specification tests", or discusses how...
This skill should be used when the user asks to "write requirements", "define requirements", "create user stories", "formalize use cases", "functional requirements", "non-functional requirements", or discusses...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.