Skip to main content
skill CX Codex

generic-code-reviewer — Claude Code skill: what it does and install

generic-code-reviewer inspects code diffs for security risks, runtime errors, bundle bloat, and WCAG AA gaps. It adapts checks to your project stack and enforces workflow rules from CLAUDE.md.

MIT 147 installs ★ 114 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add travisjneuman/.claude --skill generic-code-reviewer -a claude-code
Open on GitHub

What generic-code-reviewer does

The skill determines your tech stack directly from project files. It identifies React, Next.js, NestJS, vanilla web assets, or Python via files like package.json. Review focus shifts according to the setup, analyzing hooks, server routes, DTO decorators, or strict type annotations. It also verifies that a task summary exists in tasks/[feature-name].md before changes get committed.

Issues are categorized by severity. P0 findings halt the merge: this tier catches raw SQL injections, direct innerHTML usage, exposed secrets, and strict mode type failures. P1 handles bundle thresholds, GPU-accelerated animations, and WCAG AA accessibility rules like 4.5:1 contrast ratios. Lower P2 items cover clean code principles and dead code cleanup.

Security flaws in P0 remain non-negotiable even when checking early prototypes.

What it helps with

  • catch security gaps like unsanitized innerHTML and exposed API tokens
  • verify WCAG AA compliance including color contrast and focus rings
  • keep initial bundle sizes within configured limits
  • enforce workflow policies documented in CLAUDE.md before commits

Example prompts for the agent

  • Review the git diff for this branch before I create a commit
  • Audit this pull request against CLAUDE.md and report blockers
  • Check this frontend component for security flaws and accessibility gaps

How to install generic-code-reviewer

1Skills CLI (Vercel)

npx skills add travisjneuman/.claude --skill generic-code-reviewer -a claude-code

2Manually: put the files in place

~/.claude/skills/generic-code-reviewer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/generic-code-reviewer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about generic-code-reviewer

How do I install generic-code-reviewer in Claude Code?

Run npx skills add travisjneuman/.claude --skill generic-code-reviewer -a claude-code. The tool places the skill definition into ~/.claude/skills/generic-code-reviewer/SKILL.md.

What kind of issues will block a merge?

Any P0 issue blocks the process. This includes raw database queries, hardcoded keys, innerHTML calls, and strict compiler type errors.

Does the reviewer treat prototypes differently from production code?

Yes. It relaxes rules for experimental code, private helpers, and active feature development. However, P0 security standards are never loosened.

Source text

SKILL.md · MIT
---
name: generic-code-reviewer
description: Review code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Supports any tech stack - HTML/CSS/JS, React, TypeScript, Node.js, Python, NestJS, Next.js, and more. Use when completing features, before commits, or reviewing pull requests.
---

# Generic Code Reviewer

Review code against production quality standards. Adapts to any project's tech stack.

**Full Standards:** See [Code Review Standards](./../_shared/CODE_REVIEW_STANDARDS.md)

## CLAUDE.md Compliance

**Always check the project's CLAUDE.md for specific rules.**

**Before ANY Commit:**

- Task file exists in `tasks/[feature-name].md`
- Diff reviewed against the request, callers, and edge cases
- No console errors/warnings
- Bundle size within limits

## Tech Stack Detection

| Detection               | Stack    | Key Checks                |
| ----------------------- | -------- | ------------------------- |
| React in package.json   | React/TS | Components, hooks, state  |
| Next.js in package.json | Next.js  | SSR, API routes           |
| NestJS in package.json  | NestJS   | Guards, DTOs, services    |
| .html files, no build   | Vanilla  | Semantic HTML, minimal JS |
| .py files               | Python   | Type hints, validation    |

## P0 Issues (Block Merge)

### Security - Frontend

- Sanitize input (textContent, not innerHTML)
- `unknown` type for external data
- No exposed API keys
- HTTPS for external requests

### Security - Backend

- Input validation on all endpoints
- Auth on protected routes
- Parameterized queries (no raw SQL)
- Secrets in environment variables

### Correctness

- Logic errors that break functionality
- Type errors in strict mode
- Unhandled promise rejections

## P1 Issues (Should Fix)

### Performance

| Project Type | Target                   |
| ------------ | ------------------------ |
| Static site  | < 50KB (excluding media) |
| SPA/React    | < 100KB gzipped initial  |
| Full-stack   | < 200KB gzipped initial  |

**Animation:**

- GPU-accelerated only (transform, opacity)
- 60fps target
- Use requestAnimationFrame

### Accessibility (WCAG AA)

- Focus indicators on interactive elements
- Keyboard navigation (Tab, Enter, Escape)
- Color contrast >= 4.5:1
- ARIA labels on icon-only buttons
- Alt text for meaningful images
- Semantic HTML structure

## P2 Issues (Nice to Have)

### Code Quality

- DRY, Single Responsibility
- No magic numbers/strings
- Self-documenting code
- Follow existing patterns
- No commented-out/dead code

## Review Output Format

Only report issues found (don't list empty categories):

**Blocking Issues (P0):**

- [Only if found - security, correctness issues]

**Should Fix (P1):**

- [Only if found - performance, accessibility issues]

**Consider (P2):**

- [Only if found - code quality polish]

**If no issues:** "Code review passed. Ready to merge."

## Judgment Calls

When user asks "Is this OK?", consider:

| Context         | Stricter                       | More Lenient                    |
| --------------- | ------------------------------ | ------------------------------- |
| **Environment** | Production                     | Prototype/POC                   |
| **Path**        | Hot path, frequently executed  | One-time setup, admin only      |
| **Visibility**  | Public API, external interface | Internal helper, private method |
| **Timeline**    | Feature complete               | Active iteration                |

Adjust severity accordingly. P0 security issues are never lenient.

## Quick Checklist

**Pre-Commit:**

- [ ] Diff reviewed (inputs, edge cases, error paths, callers)
- [ ] No console errors

**Before Merge:**

- [ ] All P0 issues resolved
- [ ] P1 issues addressed or tracked
- [ ] P2 issues noted for future

## See Also

- [Code Review Standards](./../_shared/CODE_REVIEW_STANDARDS.md) - Full requirements
- [Design Patterns](./../_shared/DESIGN_PATTERNS.md) - UI consistency
- Project `CLAUDE.md` - Workflow rules

© travisjneuman · MIT · travisjneuman/.claude

Similar skills

All skills for Code review and refactoring →

From the same set117

The whole set →
generic-static-code-reviewer generic-static-code-reviewer is a skill that checks static-site HTML, CSS and JS for bugs, security issues, page weight and accessibility before a commit. CX Codex +1 149installs podcast-producer podcast-producer is a Claude Code skill that helps plan a podcast launch, prepare episodes, and create show notes. It covers the workflow from episode idea to publication. CX Codex +1 148installs generic-react-code-reviewer generic-react-code-reviewer walks your React/TypeScript diff for bugs, security holes, render costs and accessibility gaps. Fits right before a commit or when a pull request lands on your desk. CX Codex +1 148installs security This Claude Code skill covers security architecture, incident response, and vulnerability assessment. It activates for security program design, incident handling, and reviews against frameworks such as NIST and ISO 27001. CX Codex +1 148installs monitoring-observability monitoring-observability equips AI coding agents to set up OpenTelemetry, structured JSON logging, and distributed tracing. Useful when defining SLO alerts or instrumenting services. CX Codex +1 146installs codebase-documenter codebase-documenter turns a repository into readable docs: README, architecture overview, onboarding guide, API reference and code comments. Handy when someone new has to understand the project. CX Codex +1 145installs impact-report-writer The impact-report-writer skill helps structure program impact reports, choose outcome metrics, and plan data visualizations. Use it for annual reports or program evaluations. CX Codex +1 145installs frontend-enhancer frontend-enhancer polishes the visual side of a web app: palette, layout, motion, component states. Useful when the UI still reads as a stock starter. CX Codex +1 145installs

Project sponsors

Companies that keep this analytics open