skills.rest
xxih
xxihCOMMUNITY
Explore all skills by this author →
GitHub

quality-review

Review code changes and classify issues into Critical, Important, or Minor categories.

1|Updated Mar 18, 2026
Search Tags:#code-review#quality-assessment#merge-readiness#issue-classification#independent-review
One-click install
npx skills add https://github.com/xxih/ai-harness-zh --skill quality-review-xxih
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-review
Source: https://github.com/xxih/ai-harness-zh/tree/main/packages/quality-workflows/targets/codex/skills/quality-review
Command: npx skills add https://github.com/xxih/ai-harness-zh --skill quality-review-xxih

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It addresses the lack of formal, independent code review before key merges, ensuring critical issues are caught early.

Core Features & Use Cases

  • Independent reviewer priority: prefers a separate reviewer agent when available.
  • Issue classification: categorizes findings into Critical, Important, Minor.
  • Readiness assessment: outputs a clear ready or not-ready verdict.
  • Documentation: writes review summary to existing task records or .quality/quality-check.md.

Example use case: after completing a major feature or fixing a complex bug, invoke this skill to get a thorough review and decide if code is merge‑ready.

Quick Start

Ask the quality-review skill to evaluate the latest changes and indicate whether the code is ready to merge.

Frequently Asked Questions about quality-review

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

FAQPage Schema
How do I perform an independent code review before a major merge?▼

An independent code review evaluates code changes before key merges to catch critical issues early. It categorizes findings by severity and outputs a clear ready or not-ready decision for merge readiness.

How does issue classification work during a code quality assessment?▼

Issue classification during a code quality assessment categorizes review findings into Critical, Important, and Minor severity levels. This structured triage helps prioritize fixes before determining merge readiness.

When do I need a formal merge readiness check for my code changes?▼

A merge readiness check is needed at critical merge points such as major feature completions, complex bug fixes, or user-triggered review requests to ensure code changes are thoroughly vetted before integration.

How do I get a ready or not-ready decision for a complex bug fix?▼

To get a ready or not-ready decision for a complex bug fix, invoke a quality review to assess the changes independently. The review outputs a clear verdict and records the summary in task logs or a quality check file.

Can I use an independent reviewer agent for code reviews?▼

Yes, the quality review process prefers a separate independent reviewer agent when available to ensure formal assessment. This independent priority helps catch critical issues objectively before merging code.

Where are the results of a code quality assessment documented?▼

Code quality assessment results are documented by writing the review summary into existing task records or a dedicated `.quality/quality-check.md` file. This ensures merge readiness decisions are formally logged.

Related Skills

Explore More Software Engineering Skills→
greglambgreglamb
1

requesting-code-review

Dispatch a code-reviewer subagent to identify defects and readiness issues in completed code changes.

Community
Intermediate
vega113vega113

beads-reviewer

Review Beads task commits and diffs to assess merge readiness.

Community
Intermediate
JayRHaJayRHa
3

adr-author

Create immutable Architecture Decision Records with standardized structure and supersession workflow.

Community
Advanced
lengoctuong2005lengoctuong2005
5

requesting-code-review

Automate pre-commit code review with security scans, tests, and fixes.

Community
Advanced