review

Validate recent code changes across Go, Python, and TypeScript projects.

22|3|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/peteski22/claude-pragma --skill review-peteski22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/peteski22/claude-pragma/tree/main/skills/universal/review
Command: npx skills add https://github.com/peteski22/claude-pragma --skill review-peteski22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changes by executing all applicable validators and reporting results to ensure code quality and policy compliance.

Core Features & Use Cases

  • Orchestrated validation: Collects changed files, injects rules, runs deterministic checks, and aggregates results.
  • Comprehensive reporting: Produces a clear status summary including hard/should/warn violations and suggested fixes.
  • Use Case: Before merging a feature branch, run this skill to verify all validators pass and reveal any policy violations.

Quick Start

Run /review in your project to validate recent changes and see a consolidated report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review and run validators on recent changes?

Automate code review by collecting changed files, injecting rules, running deterministic checks, and aggregating results. This validator orchestration provides a comprehensive report of hard, should, and warn violations before merging branches.

What is the best way to validate code changes across Go, Python, and TypeScript projects?

Validate changes across Go, Python, and TypeScript projects by running an orchestrated central runner that injects rules and executes deterministic checks. This produces a consolidated status summary revealing any policy violations or required fixes.

Can I run automated lint and security checks locally before merging a feature branch?

Yes, you can run automated lint and security checks locally before merging. By executing the review command, the central runner applies local supplements and deterministic checks to recent code changes and reports violations.

Does automated rule injection work with my existing CI pipeline for code changes?

Automated rule injection works by collecting changed files and applying deterministic checks orchestrated by a central runner. It integrates into CI workflows to verify that validators pass and report any policy violations before merge.

How does a central runner orchestrate validators and report change status?

A central runner orchestrates validators by collecting changed files, injecting applicable rules, executing deterministic checks, and aggregating results. It outputs a clear status summary detailing hard, should, and warn violations alongside suggested fixes.

What are the limitations of using automated validators for code changes?

Automated validators are limited to deterministic checks and rule injection for Go, Python, and TypeScript projects. They report hard, should, and warn violations but require a central runner to orchestrate the validation step and aggregate results.