skills.rest
Jsplix
JsplixCOMMUNITY
Explore all skills by this author →
GitHub

code-review-review

Generate evidence-based code review feedback aligned with project quality standards.

Updated Jul 1, 2026
Search Tags:#code quality#code review#pull request#git diff#design intent#priority classification#evidence-based review
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill code-review-review-jsplix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-review
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/code-review-review
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill code-review-review-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates subjective, inconsistent code reviews by providing structured, evidence-based feedback aligned with your project's predefined code quality standards and design intent, removing guesswork from the review process and ensuring all feedback is actionable and tied to concrete criteria.

Core Features & Use Cases

  • Evidence-Aligned Feedback: All review comments are explicitly tied to specific criteria from your project's code quality guide, eliminating personal preference-based feedback.
  • Priority Classification: Review comments are sorted into p1 (must fix) to p4 (minor improvement) tiers for clear action prioritization.
  • Use Case: Ideal for software teams that want consistent, standards-aligned code reviews for feature branches, with clear, actionable feedback for implementers to reduce review back-and-forth.

Quick Start

Use the code-review-review skill to perform an evidence-based code review for your current feature branch, following the project's code quality guide and design intent.

Frequently Asked Questions about code-review-review

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

FAQPage Schema
How do I automate evidence-based code review for pull requests?▼

Evidence-based code review for pull requests is automated by evaluating feature branch git diffs against predefined project code quality guides and design intent documents, generating structured feedback with priority tiers and actionable side effect explanations.

What is priority classification in code review feedback?▼

Priority classification in code review feedback sorts comments into p1 (must fix) through p4 (minor improvement) tiers, allowing implementers to clearly prioritize action items and reduce subjective review back-and-forth.

How do I eliminate subjective comments during code review?▼

Subjective code review comments are eliminated by enforcing evidence-aligned feedback, explicitly tying every review observation to specific criteria from your project's predefined code quality guide and design intent documents.

What inputs do I need to provide for an automated code review?▼

Automated code review requires feature branch git diffs, project code quality guides, design intent documents, and pull request descriptions as mandatory inputs to generate evidence-aligned, structured review artifacts.

Can I use this for feature branch code review workflows without a design intent document?▼

No, design intent documents are mandatory inputs for feature branch code review workflows, ensuring all generated review feedback remains evidence-aligned and properly contextualized rather than subjective or guesswork-based.

Related Skills

Explore More Software Engineering Skills→
JsplixJsplix

code-review-pr-body

Generate structured pull request body drafts from git diffs.

Community
Intermediate
Avi977Avi977

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

Community
Advanced
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced