reviewer

Identify code quality issues, security risks, and maintainability concerns in code changes.

1|Updated Jun 26, 2025
One-click install
npx skills add https://github.com/Docaari/GrindfyManager --skill reviewer-docaari
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/Docaari/GrindfyManager/tree/main/.claude/skills/reviewer
Command: npx skills add https://github.com/Docaari/GrindfyManager --skill reviewer-docaari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams ensure code quality and security before merging by identifying bugs, vulnerabilities, performance issues, and technical debt.

Core Features & Use Cases

  • Automated lightweight code reviews focusing on correctness, security, and maintainability before PRs.
  • Clear, prioritized issue reporting with risk assessment to guide developers.
  • Audit-ready review artifacts that align with CI/CD pipelines and project standards.

Quick Start

Provide the code or PR you want reviewed, and I will generate a structured review with issues and recommendations.

Frequently Asked Questions about reviewer

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

FAQPage Schema
How do I review a pull request for security risks and maintainability concerns?

To review a pull request, provide the code changes to generate a structured assessment identifying security risks, maintainability concerns, and quality issues. The review produces prioritized issue reporting with risk assessment to guide developers before merging.

What is the best way to audit legacy code for compliance with project standards?

Auditing legacy code involves analyzing the module to identify technical debt, vulnerabilities, and adherence to CLAUDE.md conventions. This process generates audit-ready review artifacts that align with CI/CD pipelines and ensure compliance with project standards.

Can I use automated code review to check input validation and correctness before merge?

Yes, automated code review checks input validation and correctness by evaluating code changes against standards. It applies lightweight reviews focusing on correctness and security to catch bugs and generate prioritized recommendations before merging.

Does this code review approach work for modules with critical functionality?

Yes, this approach applies to reviews of modules with critical functionality by identifying performance issues, vulnerabilities, and technical debt. It ensures compliance with standards and satisfies requirements for structured, prioritized issue reporting.

How do I get prioritized issue reporting for technical debt and vulnerabilities?

Prioritized issue reporting is generated by providing the target code or PR for review. The analysis identifies vulnerabilities, performance issues, and technical debt, then outputs a structured review with risk assessment to guide developer fixes.

What are the limitations of automated code review for catching bugs before merge?

Automated code review focuses on correctness, security, and maintainability but relies on the provided code context. It generates audit-ready artifacts aligning with CI/CD pipelines, yet complex runtime bugs may require additional testing beyond static review.