code-review

Name: code-review
Availability: InStock
Author: tincopper

Inspects files, diffs, and pull requests for actionable, evidence-based findings.

10|Updated Mar 21, 2026

Search Tags:#code review #frontend #backend #pr review #architecture review #git diff

Ready to run

npx skills add https://github.com/tincopper/neeko --skill code-review-tincopper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/tincopper/neeko/tree/main/.omp/skills/code-review
Command: npx skills add https://github.com/tincopper/neeko --skill code-review-tincopper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform rigorous code reviews without changing the code, so you can catch quality, architecture, and maintainability issues early.

Core Features & Use Cases

Evidence-Backed Review: Inspects files, diffs, pull requests, and modules while requiring concrete file and line references for every finding.
Spec-Driven Evaluation: Uses project-specific specifications to judge correctness, error handling, layering, reuse, and long-term maintainability.
Use Case: Use it when you need a focused PR review, a module health check, or a targeted assessment of current changes before merging.

Quick Start

Ask the assistant to review the specified files, diff, or module against the project’s standards and return only findings with evidence and severity.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review a git diff for architecture and maintainability issues before merging?▼

PR review involves inspecting pull requests against project-specific specifications to judge correctness, error handling, layering, and reuse. It requires evidence-backed issue reporting with concrete file and line references to provide structured severity summaries without modifying source code.

Does code review work for both frontend and backend codebases?▼

Code review supports both frontend and backend codebases, covering file, directory, diff, pull request, and module review scenarios. It uses project-specific specifications to evaluate correctness, error handling, layering, and long-term maintainability without modifying source code.

Can I use this to check module health without modifying source code?▼

You can perform a module health check without modifying source code. The review inspects modules to assess long-term maintainability and layering, returning only actionable findings with evidence and structured severity summaries.

What is the best way to ensure code review findings are actionable?▼

The best way to ensure actionable code review findings is to require evidence-backed reporting with concrete file and line references for every issue. Findings should be evaluated against project-specific specifications and presented as structured severity summaries.

How do I evaluate pull request changes against project standards?▼

You can evaluate pull request changes against project standards by using spec-driven evaluation. This judges correctness, error handling, layering, and reuse, returning structured severity summaries with concrete file and line references for every finding.

When should I not use an automated code review approach?▼

You should not use this code review approach if you need the tool to automatically fix or modify the source code. It is designed strictly to surface actionable review findings and structured severity summaries without altering the original codebase.