Code review checklist
Skill subhansh-dev/agent-maxxing/engineering/code-review-checklist
95+ agent skills, 19 UI components, 7 system prompts from Claude Fable 5, GPT-5.5, Gemini CLI & more. Self-fine-tune your agent: paste one prompt and it reads every skill, internalizes patterns, and becomes elite. Works with Claude Code, Codex, Cursor, OpenCode + 60 more agents.
npx -y skills add subhansh-dev/agent-maxxing --skill code-review-checklistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Ship-ready code review checklist covering correctness, readability, security, performance, and frontend/backend specifics.
SKILL.md
1.7 KB, as published. Nobody here has run it
Code Review Checklist
Before shipping any code, run through this.
Does It Work?
- Runs without errors
- Handles the happy path
- Handles edge cases (null, empty, 0, negative, very large)
- Handles errors gracefully (try/catch, validation)
- No console.logs or debug code left in
Is It Readable?
- Variable names are descriptive (not
x,temp,data2) - Functions do one thing
- No magic numbers (use constants)
- Comments explain "why", not "what"
- Consistent style with existing codebase
Is It Safe?
- No SQL injection / XSS / path traversal
- No hardcoded credentials
- No secrets in logs or error messages
- Input validation on user-facing endpoints
- Rate limiting on public APIs
Is It Performant?
- No N+1 queries
- No unnecessary re-renders (React)
- No blocking operations on main thread
- Lazy loading for heavy resources
- Pagination for large datasets
Is It Maintainable?
- No code duplication (DRY)
- Clear separation of concerns
- Error messages are helpful
- Configuration is externalized
- Dependencies are pinned
Frontend-Specific
- Accessible (ARIA labels, keyboard nav, contrast)
- Responsive (mobile, tablet, desktop)
- Loading states for async operations
- Error states with recovery paths
- Empty states that guide the user
- No layout shift (CLS)
- 60fps animations (transform + opacity only)
Backend-Specific
- Database migrations are reversible
- API responses are consistent
- Rate limiting is in place
- Logging is sufficient for debugging
- Health check endpoint exists
- Graceful shutdown handling