review

Audit codebases and pull requests with a standardized checklist and automated screening.

6|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NachoOsella/DotFiles-V4 --skill review-nachoosella
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/NachoOsella/DotFiles-V4/tree/main/pi/.pi/agent/skills/review
Command: npx skills add https://github.com/NachoOsella/DotFiles-V4 --skill review-nachoosella

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews codebases or pull requests and provides structured feedback on correctness, security, performance, maintainability, testing, and documentation. This guidance helps teams audit changes before merging, catch regressions early, and raise the quality bar for code proposals.

Core Features & Use Cases

  • Systematic review of code changes with a standardized checklist covering correctness, security, performance, maintainability, testing, and documentation.
  • Automated screening using project tooling (linters, static analysis) to surface issues before manual review, with the ability to review references for deeper context.
  • Generated feedback in a concrete, actionable template, including severity classification and remediation steps, suitable for sharing with contributors and stakeholders.
  • Use Case: Pre-merge PR review in a multi-language repository to validate implementation and identify gaps in tests or docs.

Quick Start

Run the review workflow on a PR to generate a structured findings report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a structured code review on a pull request?

Perform a structured code review by applying a standardized checklist covering correctness, security, performance, maintainability, testing, and documentation. This process generates actionable findings with severity classifications and remediation steps suitable for triage.

What does automated code screening do before a manual review?

Automated code screening runs project tooling like linters and static analysis to surface issues before manual review. It reviews references for deeper context, ensuring manual reviewers focus on complex logic rather than basic formatting or syntax violations.

Can I audit a multi-language codebase for security and maintainability gaps?

Yes, you can audit a multi-language codebase for security and maintainability gaps. The review workflow applies across languages and tech stacks supported by standard linters, validating implementation and identifying missing tests or documentation.

What is the best way to catch regressions early before merging code changes?

The best way to catch regressions early before merging code changes is implementing a pre-merge review workflow. This systematically audits proposals against a comprehensive checklist, raising the quality bar and preventing defects from entering the main branch.

Does this code review process work with my existing static analysis tools?

Yes, the code review process works with existing static analysis tools. It integrates automated screening using your project's configured linters and tooling to surface issues before applying the comprehensive manual checklist for deeper context.

How should I format code review findings for stakeholders and contributors?

Format code review findings for stakeholders using a standardized template that includes severity classification and concrete remediation steps. This structured feedback approach ensures clear communication of issues across correctness, security, and maintainability dimensions.