skills.rest
UntaDotMy
UntaDotMyCOMMUNITY
Explore all skills by this author →
GitHub

reviewer

Enforce structured production-readiness reviews for code deliveries.

Updated Aug 23, 2026
Search Tags:#testing#architecture#security#review#quality-gate#code-review#production-readiness
One-click install
npx skills add https://github.com/UntaDotMy/codex_skills --skill reviewer-untadotmy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/UntaDotMy/codex_skills/tree/main/reviewer
Command: npx skills add https://github.com/UntaDotMy/codex_skills --skill reviewer-untadotmy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Production-readiness reviews and quality gates to ensure code quality, security, architecture, testing, and delivery readiness.

Core Features & Use Cases

  • Structured diff-first reviews that surface risks early
  • Evidence-backed gates to block unsafe closures and track remediation
  • Specialist routing to accelerate remediation and release confidence

Quick Start

Validate a new PR by prompting for a production-readiness review against the changeset, memory state, and SYSTEM_MAP context.

Frequently Asked Questions about reviewer

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

FAQPage Schema
How do I enforce a production-readiness review for a pull request?▼

A production-readiness review validates PR changesets against memory state and SYSTEM_MAP context to gate code quality, security, and architecture before closure.

What is a diff-first code review and when do I need it?▼

Diff-first code review evaluates actual delivery changes to surface risks early, needed for PRs, multi-file changes, and release workflows to gate production readiness.

Can I use this quality gate for multi-file changes and cross-layer deployments?▼

Yes, this quality gate applies to multi-file changes, release workflows, and cross-layer deployments, ensuring risk visibility and traceable remediation guidance.

How does specialist routing work during a code review?▼

Specialist routing directs identified risks to appropriate experts, accelerating remediation and release confidence through structured governance routing and evidence-backed gates.

What is the best way to block unsafe PR closures and track remediation?▼

Use evidence-backed quality gates enforcing production-readiness reviews to block unsafe closures, providing traceable remediation guidance and routing issues to specialists.

What are the limitations of automated production-readiness checks for release workflows?▼

Automated production-readiness checks depend on provided memory state and SYSTEM_MAP context; incomplete context limits evidence-backed gate visibility and remediation traceability.

Related Skills

Explore More Software Engineering Skills→
SnowboardTechieSnowboardTechie

dependency-review

Review dependency pull requests for risk, checks, and merge readiness.

Community
Advanced
dtyqdtyq
5.0k

code-review-expert

Review current git changes for SOLID violations, security risks, and improvements.

Official
Advanced
ollieb89ollieb89

sast-configuration

Configures SAST tools like Semgrep, SonarQube and CodeQL for automated vulnerability detection in CI/CD pipelines.

Community
Advanced
47network47network
5

sast-scanner

Scan TypeScript/JavaScript source code for OWASP-aligned security vulnerabilities.

Community
Intermediate