code-review-and-quality

Automate multi-dimensional code review across correctness, readability, architecture, security, and performance.

2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/GoBeromsu/obsidian-workspace --skill code-review-and-quality-goberomsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/GoBeromsu/obsidian-workspace/tree/main/.claude/skills/code-review-and-quality
Command: npx skills add https://github.com/GoBeromsu/obsidian-workspace --skill code-review-and-quality-goberomsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to enforce consistent, high-quality code reviews by evaluating code across multiple dimensions before merges, reducing defects and technical debt.

Core Features & Use Cases

  • Five-axis evaluation covering correctness, readability, architecture, security, and performance to guide approvals.
  • Guided decision-making that balances ideal code with project conventions and timelines.
  • Use cases include PR reviews, post-implementation validation, and cross-agent auditing of code produced by humans or AI.

Quick Start

Provide a structured code-review for a change, evaluating five axes and deciding on approval.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
What is multi-dimensional code review and why do I need it before merging?

Multi-dimensional code review evaluates changes across correctness, readability, architecture, security, and performance to reduce defects and technical debt before merges.

How do I perform an automated code review on a pull request?

Provide your code change for a structured pull request review, and the evaluation enforces checks across five axes—correctness, readability, architecture, security, and performance—to guide merge approvals.

Can I use this code review process for AI-generated code?

Yes, the code review process supports cross-agent auditing and evaluates code produced by humans or AI, applying the same five-axis checks to guide approval decisions.

Does the code review enforce best practices or allow exceptions for project conventions?

The guided decision-making balances ideal code with project conventions and timelines, ensuring the structured evaluation guides approvals without ignoring practical constraints.

What's the best way to validate architecture and security during a code review?

The best way is to enforce a structured five-axis evaluation that explicitly requires checks for architecture and security alongside correctness, readability, and performance.