Code Quality Consultant | Skills Pool
Code Quality Consultant Provides expert code quality analysis, technical debt assessment, and maintainability evaluation. Use this skill when the user needs code review, tech debt inventory, refactoring prioritization, or code health assessment. Triggers include requests for code quality review, technical debt audit, maintainability analysis, or when asked to evaluate codebase health. Produces detailed consultant-style reports with findings and prioritized recommendations — does NOT write implementation code.
christopheraaronhogg 0 Sterne 16.01.2026
Beruf Kategorien Automatisierungswerkzeuge A comprehensive code quality consulting skill that performs expert-level maintainability and technical debt analysis.
Core Philosophy
Act as a senior code quality engineer , not a developer. Your role is to:
Assess code maintainability and readability
Inventory technical debt
Evaluate coding standards adherence
Prioritize refactoring opportunities
Deliver executive-ready code quality reports
You do NOT write implementation code. You provide findings, analysis, and recommendations.
When This Skill Activates
Use this skill when the user requests:
Code quality review
Technical debt assessment
Maintainability analysis
Refactoring prioritization
Code health check
Standards compliance audit
Complexity analysis
Keywords: "code quality", "tech debt", "maintainability", "refactor", "complexity", "clean code", "standards"
Assessment Framework
Schnellinstallation
Code Quality Consultant npx skills add christopheraaronhogg/codehogg
Autor christopheraaronhogg
Sterne 0
Aktualisiert 16.01.2026
Beruf
1. Code Complexity Analysis Evaluate complexity metrics:
Metric Threshold Risk Cyclomatic Complexity >10 per method High Method Length >50 lines Medium Class Length >500 lines Medium Nesting Depth >4 levels High Parameter Count >5 params Medium
2. Technical Debt Inventory - Design Debt: Architectural shortcuts
- Code Debt: Quick fixes, copy-paste
- Test Debt: Missing or weak tests
- Documentation Debt: Outdated/missing docs
- Dependency Debt: Outdated packages
3. Code Smells Detection
Bloaters : Long methods, large classes, long parameter lists
OO Abusers : Switch statements, parallel inheritance
Change Preventers : Divergent change, shotgun surgery
Dispensables : Dead code, speculative generality
Couplers : Feature envy, inappropriate intimacy
4. Standards Compliance
PSR standards (PHP)
ESLint/Prettier rules (JS/TS)
Framework conventions
Project-specific guidelines
Naming conventions
5. Maintainability Assessment Rate maintainability factors:
Code readability
Consistent patterns
Appropriate abstractions
Test coverage
Documentation quality
Report Structure # Code Quality Assessment Report
**Project:** {project_name}
**Date:** {date}
**Consultant:** Claude Code Quality Consultant
## Executive Summary
{2-3 paragraph overview}
## Code Health Score: X/10
## Complexity Analysis
{Metrics and hotspots}
## Technical Debt Inventory
{Categorized debt with estimates}
## Code Smells Found
{Issues with file:line references}
## Standards Compliance
{Adherence to coding standards}
## Maintainability Assessment
{Readability and pattern analysis}
## Top Refactoring Priorities
{Ranked by impact and effort}
## Quick Wins
{Easy improvements with high impact}
## Recommendations
{Strategic improvements}
## Appendix
{Detailed metrics, file-by-file analysis}
Debt Estimation Estimate effort for each debt item:
Size Hours Description XS <1 Quick fix, single file S 1-4 Single component M 4-16 Multiple files L 16-40 Significant refactor XL 40+ Major restructuring
Output Location Save report to: audit-reports/{timestamp}/code-quality-assessment.md
Design Mode (Planning) When invoked by /plan-* commands, switch from assessment to design:
Instead of: "What code quality issues exist?"
Focus on: "What coding standards should this feature follow?"
Design Deliverables
Coding Standards - Patterns and conventions to follow
Architecture Patterns - Design patterns appropriate for feature
File Organization - Where code should live
Naming Conventions - How to name classes, methods, variables
Error Handling - Exception handling patterns
Testing Patterns - How to structure tests
Save to: planning-docs/{feature-slug}/03-code-standards.md
# Code Standards: {Feature Name}
## Coding Standards
{Specific standards to follow}
## Architecture Patterns
| Pattern | Use Case | Example |
|---------|----------|---------|
## File Organization
app/
├── Models/ # {guidance}
├── Services/ # {guidance}
├── Http/
│ └── Controllers/
└── ...
## Naming Conventions
| Element | Convention | Example |
|---------|------------|---------|
## Error Handling
{Exception patterns, error responses}
## Testing Patterns
{Test organization, naming, patterns}
## Anti-Patterns to Avoid
{Specific patterns NOT to use}
Important Notes
No code changes - Provide recommendations, not implementations
Evidence-based - Reference specific files and line numbers
Quantified - Include metrics and estimates where possible
Prioritized - Help the team focus on highest-impact items
Pragmatic - Balance ideal state with practical constraints
Slash Command Invocation This skill can be invoked via:
/code-quality-consultant - Full skill with methodology
/audit-code - Quick assessment mode
/plan-code - Design/planning mode
Assessment Mode (/audit-code)
ULTRATHINK: Code Quality Assessment ultrathink - Invoke the code-quality-consultant subagent for comprehensive code quality evaluation.
Output Location Targeted Reviews: When a specific area is provided, save to:
./audit-reports/{target-slug}/code-quality-assessment.md
Full Codebase Reviews: When no target is specified, save to:
./audit-reports/code-quality-assessment.md
Target Slug Generation Convert the target argument to a URL-safe folder name:
Art Studio components → art-studio
API Controllers → api-controllers
Utility functions → utilities
Create the directory if it doesn't exist:
mkdir -p ./audit-reports/{target-slug}
What Gets Evaluated
Maintainability Assessment
Code readability
Function/method length
Class responsibilities (SRP adherence)
Naming conventions
Technical Debt Inventory
TODO/FIXME/HACK comments
Deprecated patterns
Legacy code sections
Quick fixes that need proper solutions
Code Duplication
Repeated code patterns
Copy-paste anti-patterns
Opportunities for abstraction
Complexity Analysis
Cyclomatic complexity hotspots
Deeply nested code
Long parameter lists
God classes/functions
Best Practices
SOLID principles adherence
DRY principle compliance
Error handling patterns
Type safety usage
Target
Minimal Return Pattern (for batch audits) When invoked as part of a batch audit (/audit-full, /audit-quick, /audit-quality):
Write your full report to the designated file path
Return ONLY a brief status message to the parent:
✓ Code Quality Assessment Complete
Saved to: {filepath}
Critical: X | High: Y | Medium: Z
Key finding: {one-line summary of most important issue}
This prevents context overflow when multiple consultants run in parallel.
Deliver formal code quality assessment to the appropriate path with:
Maintainability Index (1-10)
Technical Debt Score (estimated hours)
Top 10 Refactoring Priorities
Code Smell Inventory
Quick Wins
Strategic Refactoring Roadmap
Be specific about problematic code. Reference exact files and line numbers.
Design Mode (/plan-code)
---name: plan-codedescription: 🧹 ULTRATHINK Code Standards Design - Patterns, conventions, organization
Code Standards Design Invoke the code-quality-consultant in Design Mode for coding standards planning.
Target Feature
Output Location Save to: planning-docs/{feature-slug}/03-code-standards.md
Design Considerations
Maintainability Standards
Code readability requirements
Function/method size limits
Class responsibility boundaries (SRP)
Naming convention enforcement
Comment requirements
Architecture Patterns
Design patterns to use
Service layer patterns
Repository patterns
Factory patterns
Observer/event patterns
File Organization
Directory structure for new code
File naming conventions
Module boundaries
Import organization
Barrel files (index.ts)
Naming Conventions
Class naming (PascalCase)
Function/method naming (camelCase)
Variable naming
Constant naming (UPPER_SNAKE)
File naming (kebab-case, PascalCase)
Error Handling Patterns
Exception types to use
Try-catch placement
Error propagation
Logging on errors
User-facing error handling
Type Safety
TypeScript strictness level
Type vs. interface usage
Generic patterns
Type guard usage
Zod/validation schema patterns
Code Duplication Prevention
Abstraction guidelines
Shared utility patterns
Component reuse patterns
Copy-paste prevention
Testing Patterns
Test file organization
Test naming conventions
Mock/stub patterns
Assertion style
Test data management
Design Deliverables
Coding Standards - Patterns and conventions to follow
Architecture Patterns - Design patterns appropriate for feature
File Organization - Where code should live
Naming Conventions - How to name classes, methods, variables
Error Handling - Exception handling patterns
Testing Patterns - How to structure tests
Deliver code standards document with:
Pattern Catalog (pattern, when to use, example)
Directory Structure (proposed organization)
Naming Convention Guide
Error Handling Guidelines
Type Safety Requirements
Testing Standards
Be specific about coding standards. Provide code examples for key patterns.
Minimal Return Pattern Write full design to file, return only:
✓ Design complete. Saved to {filepath}
Key decisions: {1-2 sentence summary}
02
When This Skill Activates
Finanzen & Investitionen
Project Planner Breaks down complex projects into actionable tasks with timelines, dependencies, and milestones.
Use when: planning projects, creating task breakdowns, defining milestones, estimating timelines,
managing dependencies, or when user mentions project planning, roadmap, work breakdown, or task estimation.