code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug, build error, broken, not working, why is X failing, check this code, security check, PR review, audit code, refactor. Also triggers when investigating 4xx or 5xx errors, deploy failures, environment variable issues, and CMS integration problems.
Profile →npx skills add rampstackco/claude-skills --skill code-review-web --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Code Review for Web Review and debug web application code with a focus on the patterns that actually break production. Stack-agnostic principles in SKILL.md. Stack-specific patterns in references. --- ## When to use - Reviewing a pull request before merging - Debugging a production issue - Investigating a build failure - Auditing security or performance of existing code - Investigating environment variable or configuration issues - Triaging a "the site is broken" report ## When NOT to use - Writing a new feature spec (use `pm-spec-writing`) - Pre-launch QA against the running site (use `qa-testing`) - Performance deep-dive on Core Web Vitals (use `performance-optimization`) - Deep accessibility compliance review (use `accessibility-audit`) --- ## Required inputs - The code, PR, error message, or symptom under review - Access to logs (build logs, function logs, server logs) if debugging - The stack (framework, hosting, database) - even at high level If just a symptom is provided ("the site is broken"), the workflow's first step is gathering enough context to investigate. --- ## The framework: 5 review dimensions Every code review covers five dimensions. Pick the depth based on the
- When to use
- When NOT to use
- Required inputs
- The framework: 5 review dimensions
- 1. Correctness
- 2. Security
- 3. Performance
- 4. Reliability
- 5. Maintainability
- Common bug patterns (stack-agnostic)
- Build and deploy
- URL and domain issues
- Cache invalidation
- Database and data
What does the code-review-web skill do?
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug, build error, broken, not working, why is X failing, check this code, security check, PR review, audit code, refactor. Also triggers when investigating 4xx or 5xx errors, deploy failures, environment variable issues, and CMS integration problems.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill code-review-web --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.