skills.rest
zxyycom
zxyycomCOMMUNITY
Explore all skills by this author →
GitHub

code-review-and-quality

Review code changes and produce severity-ordered findings with verification evidence.

Updated Jun 4, 2026
Search Tags:#performance#documentation#security#verification#code-review#findings-first
One-click install
npx skills add https://github.com/zxyycom/docnav --skill code-review-and-quality-zxyycom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/zxyycom/docnav/tree/main/.codex/skills/code-review-and-quality
Command: npx skills add https://github.com/zxyycom/docnav --skill code-review-and-quality-zxyycom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code review is often slow and subjective; this skill enforces a findings-first approach that surfaces issues by severity and links each finding to the touched files to guide faster resolution and safer approvals.

Core Features & Use Cases

  • Findings-first verdicts ordered by severity, with actionable items bound to specific files/lines.
  • Workflow guidance and ownership tracing across touched surfaces (core CLI, adapters, ref generation, pagination, raw/readable output, schema, MCP/OpenSpec artifacts).
  • Verification evidence requirements including tests, fixtures, docs, and governance boundaries to support observable behavior and security/performance assessments.

Quick Start

Analyze the latest PR changes and produce a findings-first review following the skill's output format.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
How do I perform a findings-first code review for a PR?▼

Findings-first code review for a PR surfaces issues ordered by severity and links each finding to specific touched files and lines. This structured approach enforces faster resolution and safer approvals by prioritizing actionable items bound to evidence.

What is a findings-first approach for code changes and approvals?▼

A findings-first approach for code changes enforces a structured output with severity-based findings, validating evidence from tests, fixtures, and docs. It delivers a clear verification and verdict to guide safer approvals across core CLI, adapters, and schema artifacts.

How do I verify test evidence and governance boundaries during a code review?▼

To verify test evidence and governance boundaries during a code review, validate behavioral changes against tests, fixtures, and documentation. This ensures observable behavior and security performance assessments are met before delivering a final approval verdict.

Can I review local diffs and agent handoffs using a severity-based format?▼

Yes, you can review local diffs and agent handoffs using a severity-based format. The review applies to code changes across core CLI, ref generation, pagination, raw output, schema, and MCP OpenSpec artifacts, enforcing structured verification.

Does this code review skill support ownership tracing across touched surfaces?▼

Yes, the code review skill supports ownership tracing across touched surfaces. It provides workflow guidance for changes spanning core CLI, adapters, pagination, raw readable output, schema, and MCP OpenSpec artifacts to ensure comprehensive governance.

Related Skills

Explore More Software Engineering Skills→
grtninjagrtninja
2

repo-c-boundary-governance

Enforce architecture and governance boundaries across code changes and documentation.

Community
Intermediate
wesuuuwesuuu

td_fix

Resolve open technical debt items from TECH_DEBT.md with tests.

Community
Advanced
plaitedplaited
6

headless-adapters

Generate and validate headless CLI adapters from JSON schemas.

Official
Intermediate
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic