generic-fullstack-code-reviewer — Claude Code skill
generic-fullstack-code-reviewer is a Claude Code skill for reviewing full-stack changes before commits and during pull request reviews. It checks Next.js and NestJS code for bugs, security issues, and project-rule mismatches.
MIT 157 installs ★ 114 updated 2026-10-25
npx skills add travisjneuman/.claude --skill generic-fullstack-code-reviewer -a claude-codeWhat generic-fullstack-code-reviewer does
The skill reviews Next.js and NestJS changes for route protection, input validation, database query safety, and agreement between frontend and backend types. It also checks environment variables, secrets, and Prisma migrations.
Its review uses the diff rather than running tests, linting, or a build. It draws on the P0/P1/P2 priorities and review method of the Generic Code Reviewer skill. Test cases are covered when the user asks for tests.
What it helps with
- spot a protected route without an auth guard
- check whether DTOs validate incoming values
- find raw SQL queries
- compare shared API types across frontend and backend
- catch
.envfiles included in a commit
Example prompts for the agent
- Review my Next.js and NestJS changes before I commit them.
- Review this pull request for auth, DTO validation, and database query issues.
- Check the diff after my Prisma schema changes and flag migration problems.
How to install generic-fullstack-code-reviewer
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-code-reviewer -a claude-code2Manually: put the files in place
~/.claude/skills/generic-fullstack-code-reviewer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/generic-fullstack-code-reviewer/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-code-reviewer -a codex2Manually: put the files in place
.agents/skills/generic-fullstack-code-reviewer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-code-reviewer -a cursor2Manually: put the files in place
.cursor/skills/generic-fullstack-code-reviewer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install travisjneuman/.claude skills/generic-fullstack-code-reviewer2Manually: put the files in place
.github/skills/generic-fullstack-code-reviewer/SKILL.md1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-code-reviewer -a gemini-cli2Platform CLI
gemini skills install https://github.com/travisjneuman/.claude --path skills/generic-fullstack-code-reviewerManually: put the files in place
.devin/skills/generic-fullstack-code-reviewer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-code-reviewer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about generic-fullstack-code-reviewer
How do I install generic-fullstack-code-reviewer in Claude Code?
Run npx skills add travisjneuman/.claude --skill generic-fullstack-code-reviewer -a claude-code. The skill file is at ~/.claude/skills/generic-fullstack-code-reviewer/SKILL.md.
What does generic-fullstack-code-reviewer do?
It reviews full-stack changes in Next.js and NestJS for bugs, security problems, and mismatches between frontend and backend code. It also checks Prisma and environment secrets.
How does generic-fullstack-code-reviewer review code?
It reads the diff instead of running a test, lint, and build sequence. Tests come into scope when the user requests them.
Source text
SKILL.md · MIT
---
name: generic-fullstack-code-reviewer
description: Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.
---
# Fullstack Code Reviewer
Review Next.js/NestJS code against production quality standards.
**Extends:** [Generic Code Reviewer](../generic-code-reviewer/SKILL.md) - Read base skill for full code review methodology, P0/P1/P2 priority system, and judgment calls.
## Pre-Commit Validation
Validate by reading the diff, not by running a test/lint/build ladder; the checks below are what to look for.
## Fullstack-Specific Checks
### Backend (NestJS)
**Authentication & Authorization:**
```typescript
// Protected routes MUST have auth guard
@UseGuards(JwtAuthGuard)
@Get('profile')
getProfile(@CurrentUser() user: User) {
return this.userService.findById(user.id);
}
```
**Input Validation (DTOs):**
```typescript
// All inputs validated via class-validator
export class CreateUserDto {
@IsEmail()
email: string;
@IsString()
@MinLength(8)
password: string;
}
```
**Database Safety:**
```typescript
// Use Prisma, never raw SQL
// ✓ Good
await this.prisma.user.findUnique({ where: { id } });
// ✗ Bad
await this.prisma.$queryRaw`SELECT * FROM users WHERE id = ${id}`;
```
### Frontend (Next.js)
**Server vs Client Components:**
```typescript
// Default: Server Component (can fetch data, no hooks)
export default async function Page() {
const data = await getData();
return <div>{data}</div>;
}
// Client: Interactive (hooks, event handlers)
'use client';
export default function Interactive() {
const [state, setState] = useState();
return <button onClick={() => setState(...)}>Click</button>;
}
```
**API Route Patterns:**
```typescript
// app/api/[route]/route.ts
export async function POST(request: Request) {
const body = await request.json();
// Validate body before processing
return NextResponse.json({ success: true });
}
```
### Cross-Stack Consistency
**Shared Types:**
```typescript
// types/api.ts - Shared between frontend/backend
interface UserResponse {
id: string;
email: string;
createdAt: string;
}
```
**API Contract:**
- Request DTOs match frontend payloads
- Response types match frontend expectations
- Error format consistent (status, message, errors[])
### Environment & Secrets
```bash
# .env (never committed)
DATABASE_URL=postgres://...
JWT_SECRET=...
# Check .env.example exists with placeholder values
# Verify .gitignore includes .env
```
## Prisma Checks
```bash
# After schema changes
npx prisma migrate dev --name description
npx prisma generate
```
- Migrations are reversible
- Types regenerated after schema changes
- Relations properly defined
## Testing Patterns (when the user asks for tests)
**Backend:**
- Unit tests for services
- E2E tests for API endpoints
- Mocked database for tests
**Frontend:**
- Component tests for interactivity
- API mocking for integration tests
## Quick Fullstack Checklist
- [ ] Auth guards on protected routes
- [ ] DTOs validate all inputs
- [ ] No raw SQL queries
- [ ] Shared types match
- [ ] .env not committed
- [ ] Prisma types current
## See Also
- [Generic Code Reviewer](../generic-code-reviewer/SKILL.md) - Base methodology
- [Code Review Standards](../_shared/CODE_REVIEW_STANDARDS.md) - Full requirements
- [Design Patterns](../_shared/DESIGN_PATTERNS.md) - UI consistency
© travisjneuman · MIT · travisjneuman/.claude