code-review

Automate code reviews to identify security, performance, and maintainability issues.

7.0k|977|Updated May 11, 2023
One-click install
npx skills add https://github.com/kyegomez/swarms --skill code-review-kyegomez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/kyegomez/swarms/tree/main/examples/single_agent/agent_skill_examples/code-review
Command: npx skills add https://github.com/kyegomez/swarms --skill code-review-kyegomez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides and standardizes the process of evaluating code across projects, ensuring critical quality gates are consistently applied and documented.

Core Features & Use Cases

  • Code Quality Evaluation: Assess readability, naming, structure, and test coverage.
  • Security & Compliance: Identify common vulnerabilities and architectural risks.
  • Maintainability & Best Practices: Highlight technical debt, abstractions, and dependency health.
  • Use Case: When reviewing a PR, run this skill to generate a repeatable checklist and a prioritized remediation plan.

Quick Start

To begin a review, provide the target repository URL and pull request number. The skill will return a structured report detailing findings, recommendations, and actionable items for the team.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code reviews for pull requests to check security and performance?

Automated code reviews apply a structured checklist to pull requests, evaluating security vulnerabilities, performance bottlenecks, and maintainability issues. This process generates a prioritized remediation plan and consistent review templates to standardize quality gates across projects.

What is the best way to identify technical debt and maintainability issues during development?

Identifying technical debt during development involves applying standardized code quality evaluations that highlight architectural risks, poor abstractions, and dependency health. This approach outputs actionable items for the team, ensuring consistent remediation and improved maintainability across the codebase.

Can I use static analysis to evaluate code quality and architecture decisions across multiple programming languages?

Static analysis for code quality evaluation applies to pull requests across languages by assessing readability, naming conventions, and structure. It uses reproducible evaluation criteria to ensure consistent outputs regardless of the programming language used in the repository.

How do I generate a reproducible checklist and remediation plan for a pull request?

Generating a reproducible checklist and remediation plan requires providing the target repository URL and pull request number. The automated review then returns a structured report detailing findings, recommendations, and actionable items for the team.

Does this automated code review tool require any specific dependencies or environment setup?

This automated code review tool requires no dependencies or environment setup. It operates without external components, directly evaluating code quality, security, and maintainability based on the provided repository URL and pull request number.

When should I not use an automated code review checklist for evaluating pull requests?

Automated code review checklists are not suitable for evaluating subjective business logic or highly context-specific architectural decisions. They apply reproducible evaluation criteria for standard quality gates but cannot replace human judgment for complex domain logic.