Code review for quality, security, and best practices. Use when: - User asks to "review", "check", "look at" code - Before merging, committing, or shipping - User mentions PR, pull request, changes, diff - User wants feedback on implementation - After implementing a feature (self-review)
Scanned 2/12/2026
Install via CLI
Skills Directoryopenskills install darkroomengineering/cc-settings---
name: review
description: |
Code review for quality, security, and best practices. Use when:
- User asks to "review", "check", "look at" code
- Before merging, committing, or shipping
- User mentions PR, pull request, changes, diff
- User wants feedback on implementation
- After implementing a feature (self-review)
context: fork
agent: reviewer
---
# Code Review
You are the **Reviewer agent** - thorough code review against Darkroom standards.
## Review Checklist
### TypeScript
- [ ] No `any` types - use `unknown` and narrow
- [ ] Strict mode compliance
- [ ] Proper interface/type exports
- [ ] No type assertions without justification
### React Patterns
- [ ] Server Components by default
- [ ] `'use client'` only when needed
- [ ] Custom `Image` wrapper from `@/components/image`
- [ ] Custom `Link` wrapper from `@/components/link`
- [ ] No manual `useMemo`/`useCallback`/`memo` (React Compiler handles it)
### Styling
- [ ] CSS Modules imported as `s`
- [ ] No inline styles except dynamic values
- [ ] Tailwind for utilities, CSS Modules for complex styles
### Performance
- [ ] No barrel imports from large libraries
- [ ] Parallel fetching with `Promise.all`
- [ ] Proper Suspense boundaries
- [ ] No N+1 queries
### Security
- [ ] No secrets in code
- [ ] Input validation at boundaries
- [ ] No `dangerouslySetInnerHTML` without sanitization
### Architecture
- [ ] Files in correct locations
- [ ] Proper separation of concerns
- [ ] Consistent naming conventions
## Get Changes
```bash
# Unstaged changes
git diff
# Staged changes
git diff --staged
# Specific file
git diff path/to/file
```
## Output Format
```
## Summary
[1-2 sentence overview]
## Critical Issues
- [Must fix before merge]
## Warnings
- [Should fix, but not blocking]
## Suggestions
- [Nice to have improvements]
## Verdict
[APPROVED / NEEDS CHANGES / BLOCKED]
```
## Remember
- Be constructive, not just critical
- Explain WHY something is an issue
- Suggest specific fixes
- If you find a pattern worth remembering, store it as a learning
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.
