agentsclimarketplace

Code review

Skill dewitt4/claude-code-template/.claude/skills/code-review

Use this template to launch a Claude Code development workflow with project plan, skills, plug-ins, and MCP servers

Install
npx -y skills add dewitt4/claude-code-template --skill code-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 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

Perform comprehensive code reviews focusing on best practices, security, performance, maintainability, and code quality

SKILL.md

2.3 KB, as published. Nobody here has run it

Code Review Skill

When performing code reviews, follow this systematic approach:

Review Checklist

1. Code Quality

  • Readability: Is the code easy to understand? Are variable and function names descriptive?
  • Simplicity: Is the code as simple as it can be? Any unnecessary complexity?
  • DRY Principle: Is there code duplication that should be abstracted?
  • Consistency: Does the code follow project conventions and style guidelines?

2. Functionality

  • Correctness: Does the code do what it's supposed to do?
  • Edge Cases: Are edge cases and error conditions handled?
  • Logic: Is the logic sound and easy to follow?
  • Testing: Are there adequate tests? Do they cover important scenarios?

3. Security

  • Input Validation: Is user input properly validated and sanitized?
  • Authentication/Authorization: Are security checks in place?
  • Sensitive Data: Is sensitive data properly protected?
  • Dependencies: Are dependencies up-to-date and secure?

4. Performance

  • Efficiency: Are there any obvious performance issues?
  • Resource Usage: Is memory and CPU usage reasonable?
  • Scalability: Will this code scale with increased load?
  • Database Queries: Are queries optimized (N+1 problems, indexes)?

5. Maintainability

  • Documentation: Is complex logic documented?
  • Error Handling: Are errors handled gracefully with helpful messages?
  • Modularity: Is the code properly modularized?
  • Technical Debt: Does this introduce or reduce technical debt?

Review Format

Provide feedback in this structure:

✅ Strengths

List what the code does well

⚠️ Issues Found

Categorize by severity:

  • Critical: Security issues, bugs, data loss risks
  • Major: Performance problems, architectural concerns
  • Minor: Style issues, minor improvements

💡 Suggestions

Specific, actionable recommendations with code examples when helpful

📝 Summary

Brief overall assessment and priority recommendations

Tone

  • Be constructive and respectful
  • Explain the "why" behind suggestions
  • Offer alternatives when criticizing
  • Acknowledge good practices

Gives 0 of the 12 instructions most code review skills give

Counted across 610 of the 674 authors here whose files we hold, read 2026-08-06

  • push back with technical reasoning if wrongin 60 of 610, across 24 files
  • ask for clarification on unclear itemsin 51 of 610, across 16 files
  • fix critical issues immediatelyin 45 of 610, across 29 files
  • implement one item at a timein 45 of 610, across 11 files
  • group findings by severityin 44 of 610, across 43 files
  • verify feedback against the codebasein 42 of 610, across 8 files
  • dispatch a code reviewer subagentin 39 of 610, across 23 files
  • fix important issues before proceedingin 37 of 610, across 22 files
  • test each fix individuallyin 35 of 610, across 7 files
  • reply in github comment threadsin 33 of 610, across 5 files
  • check for security vulnerabilitiesin 31 of 610, across 27 files
  • factualize corrections without over-explainingin 30 of 610, across 2 files

Said here and by no other author read

  • identify untested or undocumented logic
  • offer alternatives when criticizing code

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.