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
- 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)
Coordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
>-
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.