code-review-patterns
The code-review-patterns skill performs systematic code assessment across four dimensions: security, quality, performance, and maintainability, each weighted by importance. It reports only high-confidence findings (80% or above) with severity classification and remediation guidance, while treating empty catch blocks as critical violations. Use this skill during code review stages in BUILD, DEBUG, and REVIEW workflows to generate structured assessments with Router Contract status indicators.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/code-review-patterns && cp -r /tmp/code-review-patterns/library/methodologies/cc10x/skills/code-review-patterns ~/.claude/skills/code-review-patternsSKILL.md
# Code Review Patterns ## Overview Structured patterns for multi-dimensional code review with strict confidence gating. Only issues with >=80% confidence are reported. Zero tolerance for empty catch blocks. ## Four Dimensions ### Security (weight: 30%) - Injection vulnerabilities (SQL, XSS, command) - Authentication and authorization patterns - Secrets handling (no hardcoded credentials) - Input validation and sanitization ### Quality (weight: 25%) - Naming conventions and consistency - Code structure (SRP, cohesion, coupling) - Error handling completeness - Type safety (no `any` escapes) ### Performance (weight: 20%) - Algorithmic complexity (flag O(n^2) or worse) - Resource and memory leaks - Database query efficiency (N+1) - Caching opportunities ### Maintainability (weight: 25%) - Documentation (JSDoc/TSDoc for public APIs) - Test coverage adequacy - Readability (function length, nesting depth) - Tech debt markers (TODO, FIXME) ## Confidence Gating - Only report issues with confidence >= 80% - Empty catch blocks are always critical (100% confidence) - Classify: critical, high, medium, low - Include actionable remediation for each issue ## Router Contract Every review must produce: STATUS, BLOCKING, REQUIRES_REMEDIATION, issue counts. ## When to Use - Code review step in BUILD workflow - Fix review in DEBUG workflow - Full REVIEW workflow ## Agents Used - `code-reviewer` (primary consumer) - `silent-failure-hunter` (error handling dimension)
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement