code-review

Analyze proposed code changes and generate structured review feedback.

39|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/hffmnnj/opencode-goopspec --skill code-review-hffmnnj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/hffmnnj/opencode-goopspec/tree/main/skills/code-review
Command: npx skills add https://github.com/hffmnnj/opencode-goopspec --skill code-review-hffmnnj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are essential to improve quality, share knowledge, and prevent defects, but they can be inconsistent, time-consuming, and siloed. This Skill provides a structured, constructive review framework to standardize feedback and elevate code quality across teams.

Core Features & Use Cases

  • Structured Feedback: Consistent, actionable comments covering correctness, design, performance, security, and maintainability.
  • Knowledge Sharing: Document rationale and best practices to uplift team skills.
  • Use Case: Apply during pull requests to quickly assess changes, leave actionable feedback, and track improvement over time.

Quick Start

Provide a sample PR diff or code snippet and ask the Skill to generate a comprehensive review focusing on correctness and maintainability. For example: "Review the following function for edge cases and readability: function foo(bar){...}"

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I provide effective code review feedback on pull requests?

Effective code review feedback addresses correctness, design, performance, security, and maintainability in a structured format. This Skill generates actionable comments that distinguish blockers from suggestions, guide developers toward acceptance criteria, and document rationale to share knowledge across your team.

What should I focus on when reviewing code for quality and maintainability?

Code review should evaluate correctness for bugs and edge cases, design for clarity and architecture, performance for efficiency, security for vulnerabilities, and maintainability for readability and technical debt. This Skill applies a consistent framework covering all five dimensions to standardize feedback.

How can code reviews reduce defects and improve team knowledge?

Structured code reviews catch defects early, prevent regressions, and document best practices through actionable feedback. By standardizing review criteria and rationale, teams build shared understanding and elevate coding standards over time.

Can I use this for reviewing code changes in typical pull request workflows?

Yes. This Skill is designed for pull request scenarios and generates thorough, constructive review feedback. Provide a PR diff or code snippet and receive comprehensive analysis with structured comments and clear identification of critical issues versus improvement suggestions.

What's the difference between blocking issues and suggestions in code review?

Blocking issues are correctness, security, or design problems that must be resolved before merge. Suggestions improve maintainability, performance, or style without blocking. This Skill identifies and labels each category clearly so developers understand priority and scope.

Why is consistent code review feedback important for teams?

Inconsistent reviews create confusion, miss defects, and waste time. Standardized feedback ensures all code meets the same quality bar, reduces rework cycles, and builds team alignment on what "done" means, accelerating development velocity.