cx-review

Automate structured code reviews for bugs, style deviations, and security concerns.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/AngelMaldonado/skills --skill cx-review
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: cx-review
Source: https://github.com/AngelMaldonado/skills/tree/main/.claude/skills/cx-review
Command: npx skills add https://github.com/AngelMaldonado/skills --skill cx-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes code reviews to ensure quality, adherence to conventions, and thorough evaluation of changes, PRs, and documentation.

Core Features & Use Cases

  • Load change context and read diffs to understand the change scope.
  • Check against project conventions and .cx/cx.yaml rules to enforce consistency.
  • Provide precise, actionable feedback with references and suggested improvements.

Quick Start

Ask Claude Code to perform a code review on the latest pull request and surface actionable feedback.

Frequently Asked Questions about cx-review

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

FAQPage Schema
How do I automate a code review for a pull request?β–Ό

Automated code review loads change context and inspects diffs to identify bugs, style deviations, and security concerns in pull requests. It ensures changes conform to project conventions and .cx/cx.yaml rules, providing precise, actionable feedback for developers.

Can I enforce project conventions during a code review?β–Ό

Yes, enforcing project conventions during code review checks changes against .cx/cx.yaml rules. The review process reads diffs and evaluates conformity to project standards, surfacing precise feedback with references and suggested improvements to maintain consistency.

How do I check pull request diffs for security concerns and bugs?β–Ό

Checking pull request diffs for security concerns and bugs requires loading change context and inspecting the modified code. Automated review identifies potential vulnerabilities, style deviations, and logical errors, ensuring changes meet project quality and security standards.

What is the best way to provide actionable feedback on code changes?β–Ό

Providing actionable feedback on code changes involves structuring the review to reference specific deviations from project conventions and .cx/cx.yaml rules. This approach ensures feedback includes suggested improvements directly tied to the identified bugs or security concerns.

Do I need configuration rules to perform a structured code review?β–Ό

Yes, configuration rules in .cx/cx.yaml are required to enforce consistency during structured code reviews. The review process checks diffs against these specific project conventions to provide precise, actionable feedback and ensure quality adherence.