code-reviewer

Name: code-reviewer
Availability: InStock
Author: mxnyawi

Review pull request code changes for correctness, security, and maintainability.

Updated Jan 25, 2026

Search Tags:#linting #feedback #code-quality #static-analysis #code-review #pull-request #review-process

Ready to run

npx skills add https://github.com/mxnyawi/opencode-standup --skill code-reviewer-mxnyawi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/mxnyawi/opencode-standup/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/mxnyawi/opencode-standup --skill code-reviewer-mxnyawi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Code Reviewer role provides a disciplined approach to evaluating code changes, catching defects, and enforcing coding standards across PRs to raise overall code quality.

Core Features & Use Cases

Review all code changes (PRs) from developers to identify issues, suggest refactors, and improve readability.
Provide structured, actionable feedback with clear next steps and traceable decisions.
Maintain consistency with project standards by documenting guidelines and logging progress in dedicated per-project files.

Quick Start

Instruct the AI to perform a thorough code review of a given PR and document results in the logs and tasks.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I perform a structured code review on a pull request?▼

Identify and assess code changes in pull requests by applying a structured review workflow that evaluates correctness, security, maintainability, and documentation to improve overall code quality.

What is the best way to enforce coding standards and provide actionable feedback during a code review?▼

The best way to enforce coding standards is by applying a structured review workflow across projects that generates clear, actionable feedback, logs progress in per-project files, and escalates critical issues when needed.

Can I use static analysis and linting to assess maintainability and security in code changes?▼

Yes, static analysis and linting are evaluated alongside code changes to assess maintainability and security. This ensures the review process catches defects and raises overall code quality consistently across pull requests.

How do I track code review progress and document decisions for different projects?▼

Track code review progress by recording decisions and actionable outcomes in dedicated per-project logs and task trackers. This maintains consistency with project standards and ensures traceable feedback for developers.

When should I escalate critical issues found during a pull request review?▼

Escalate critical issues found during a pull request review when defects threaten correctness or security. The review workflow identifies these severe defects and escalates them to maintain code quality and enforce standards.