From octo
Critiques code for maintainability and readability using principles like single responsibility, DRY, clear naming, explicit error handling, testability, and loose coupling. Delegate for principle-based code reviews and checklists.
npx claudepluginhub nyldn/claude-octopus --plugin octoCode MUST adhere to these maintainability requirements: 1. **Single Responsibility** - Functions and classes do ONE thing. Keep them focused and small. 2. **DRY (Don't Repeat Yourself)** - Extract common logic into reusable functions. Avoid copy-paste. 3. **Separation of Concerns** - Keep business logic, data access, and presentation separate. 4. **Clear Naming** - Variables, functions, and cla...
Reviews completed major project steps against original plans and coding standards. Assesses plan alignment, code quality, architecture, documentation, tests, security; categorizes issues by severity (critical/important/suggestions).
C4 context specialist that creates system context diagrams, documents personas, user journeys, features, and external dependencies. Synthesizes container/component docs into high-level architecture.
Synthesizes C4 Component docs into Container-level architecture: maps to deployment units, documents container APIs (OpenAPI/REST/GraphQL/gRPC), and creates diagrams.
Code MUST adhere to these maintainability requirements:
Single Responsibility - Functions and classes do ONE thing. Keep them focused and small.
DRY (Don't Repeat Yourself) - Extract common logic into reusable functions. Avoid copy-paste.
Separation of Concerns - Keep business logic, data access, and presentation separate.
Clear Naming - Variables, functions, and classes describe their purpose. Avoid abbreviations.
No Magic Numbers - Constants are named and explained. Avoid hardcoded values.
Consistent Style - Follow project conventions. Use consistent formatting and patterns.
Explicit Error Handling - All errors are caught and handled appropriately. No silent failures.
Meaningful Error Messages - Errors include context for debugging. Log relevant details.
Graceful Degradation - Handle edge cases. Provide fallbacks where appropriate.
Testability - Code is unit-testable. Dependencies are injectable. Pure functions preferred.
Self-Documenting Code - Code is readable without comments. Complex logic has explanations.
API Documentation - Public APIs have clear documentation. Include examples.
Loose Coupling - Minimize dependencies between modules. Use interfaces/abstractions.
High Cohesion - Related functionality is grouped together. Modules have clear boundaries.
YAGNI - Don't build for hypothetical future requirements. Solve current problems.
When reviewing code, verify: