agentsclimarketplace

Code review

Skill henriquescastilho/my-claude/.claude/skills/code-review

Setup público e sanitizado de um Claude Code full-stack: 8 sub-agents com roteamento por modelo, 792 skills, hooks de segurança, MCP servers e metodologia opinativa. Desenhado para um agente de IA se auto-configurar.

Install
npx -y skills add henriquescastilho/my-claude --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.
  • 1 stars1 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.

SKILL.md

2.6 KB, as published. Nobody here has run it

<!-- Source: claude-code-templates/utilities/code-review.md -->

allowed-tools: Read, Bash, Grep, Glob argument-hint: [file-path] | [commit-hash] | --full description: Comprehensive code quality review with security, performance, and architecture analysis

Code Quality Review

Perform comprehensive code quality review: $ARGUMENTS

Current State

  • Git status: !git status --porcelain
  • Recent changes: !git diff --stat HEAD~5
  • Repository info: !git log --oneline -5
  • Build status: !npm run build --dry-run 2>/dev/null || echo "No build script"

Task

Follow these steps to conduct a thorough code review:

  1. Repository Analysis

    • Examine the repository structure and identify the primary language/framework
    • Check for configuration files (package.json, requirements.txt, Cargo.toml, etc.)
    • Review README and documentation for context

  2. Code Quality Assessment

    • Scan for code smells, anti-patterns, and potential bugs
    • Check for consistent coding style and naming conventions
    • Identify unused imports, variables, or dead code
    • Review error handling and logging practices

  3. Security Review

    • Look for common security vulnerabilities (SQL injection, XSS, etc.)
    • Check for hardcoded secrets, API keys, or passwords
    • Review authentication and authorization logic
    • Examine input validation and sanitization

  4. Performance Analysis

    • Identify potential performance bottlenecks
    • Check for inefficient algorithms or database queries
    • Review memory usage patterns and potential leaks
    • Analyze bundle size and optimization opportunities

  5. Architecture & Design

    • Evaluate code organization and separation of concerns
    • Check for proper abstraction and modularity
    • Review dependency management and coupling
    • Assess scalability and maintainability

  6. Testing Coverage

    • Check existing test coverage and quality
    • Identify areas lacking proper testing
    • Review test structure and organization
    • Suggest additional test scenarios

  7. Documentation Review

    • Evaluate code comments and inline documentation
    • Check API documentation completeness
    • Review README and setup instructions
    • Identify areas needing better documentation

  8. Recommendations

    • Prioritize issues by severity (critical, high, medium, low)
    • Provide specific, actionable recommendations
    • Suggest tools and practices for improvement
    • Create a summary report with next steps

Remember to be constructive and provide specific examples with file paths and line numbers where applicable.

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.