skills.rest
foutoucour
foutoucourCOMMUNITY
Explore all skills by this author →
𝕏@jordiriera_cgGitHub

code-reviewer

Analyze code changes in pull requests and diffs for bugs, security issues, and maintainability problems.

Updated Mar 24, 2026
Search Tags:#security#maintainability#quality#bugs#code-review#pull-request#diff-analysis
One-click install
npx skills add https://github.com/foutoucour/guitar-match --skill code-reviewer-foutoucour
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/foutoucour/guitar-match/tree/main/.claude/skills/code-reviewer
Command: npx skills add https://github.com/foutoucour/guitar-match --skill code-reviewer-foutoucour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review teams struggle to catch bugs, security issues, and maintainability problems in code changes during fast-paced PR reviews. This Skill helps surface those issues before merging, reducing post-merge defects and technical debt.

Core Features & Use Cases

  • Automated code-review of diffs and pull requests across languages and frameworks
  • Severity-based findings with actionable remediation suggestions
  • Clear, developer-friendly outputs that integrate with CI/CD workflows

Quick Start

Provide a PR URL or file path to analyze.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a pull request for bugs and security issues before merging?▼

Review a pull request for bugs and security issues by analyzing the diff. Provide a PR URL or file path to an automated code-review tool to surface maintainability problems and severity-based findings before merging.

Can I use automated code review across different programming languages and frameworks?▼

Automated code review can analyze diffs across languages and frameworks. It applies severity classification and structured findings output to identify bugs and security issues regardless of the specific technology stack.

What is the best way to integrate pre-merge diff analysis into a CI/CD workflow?▼

The best way to integrate pre-merge diff analysis into a CI/CD workflow is using developer-friendly outputs from automated code review. This provides actionable remediation suggestions and severity-based findings directly in your pipeline.

How do I classify the severity of maintainability problems found in a code diff?▼

Classify the severity of maintainability problems by applying structured diff analysis to the code changes. This process identifies bugs and security issues, categorizing them by severity to produce actionable remediation suggestions.

Does automated code review work for post-change audits as well as pre-merge checks?▼

Automated code review works for both pre-merge reviews and post-change audits. It analyzes code changes to identify bugs, security issues, and maintainability problems, ensuring scalable diff analysis whenever needed.

Why does my pull request review miss maintainability problems during fast-paced development?▼

Pull request reviews miss maintainability problems during fast-paced development due to manual oversight limits. Automated diff analysis surfaces these issues before merging, reducing post-merge defects and technical debt.

Related Skills

Explore More Software Engineering Skills→
RonnasaydRonnasayd
1

generate-pr-description

Generate structured Pull Request descriptions from git diffs and commit history.

Community
Intermediate
h4vzzh4vzz
33

Code Review

Automate multi-dimensional code reviews with severity-ranked, line-level feedback.

Community
Advanced
winsorllcwinsorllc

code-review

Execute linters, static analysis, and security scanners on code.

Community
Intermediate
arthtyagiarthtyagi
1

benchmark-sandbox

Provision Vercel Sandboxes to run benchmark scenarios and generate coverage reports.

Community
Advanced