review-pr

Map pull request changed files to subsystem review sections and generate tasks.

11|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/lightseekorg/smg-dev-guide --skill review-pr-lightseekorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/lightseekorg/smg-dev-guide/tree/main/skills/review-pr
Command: npx skills add https://github.com/lightseekorg/smg-dev-guide --skill review-pr-lightseekorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Difficulty ensuring PR reviews cover all touched subsystems; this skill maps changed files to subsystem sections and enforces a complete, subsystem-aware review workflow.

Core Features & Use Cases

  • Maps changed files to checklist sections using a file-to-section mapping.
  • Creates one review task per matched section and uses anti-patterns guidance to flag issues.
  • Provides a structured summary to ensure comprehensive PR governance across subsystems.

Quick Start

Review a PR by mapping changed files to subsystem sections and generating review tasks for each matched area.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I ensure PR reviews cover all touched subsystems?

To ensure PR reviews cover all touched subsystems, this skill maps changed files in a pull request to subsystem-specific review sections and enforces a comprehensive, subsystem-aware review workflow.

What is the best way to automate code review checklists for a pull request?

Automating code review checklists involves mapping changed PR files to a predefined file-to-section mapping, which creates one review task per matched section to systematically flag anti-patterns.

Can I map changed files to specific subsystem review sections automatically?

Yes, you can automatically map changed files to specific subsystem review sections by providing a PR diff and a file-to-section mapping, which generates targeted reviewer tasks for each impacted area.

How do code reviews use anti-patterns references for quality gates?

Code reviews use anti-patterns references for quality gates by consulting them during automatic task generation to flag governance issues and ensure structured PR compliance across subsystems.

What do I need to generate subsystem-aware review tasks?

To generate subsystem-aware review tasks, you need the PR diff, a file-to-section mapping, and an anti-patterns reference to guide the governance checks for each matched section.