paw-review-understanding

Analyze PR changes to generate ReviewContext.md and DerivedSpec.md artifacts.

39|6|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-understanding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paw-review-understanding
Source: https://github.com/lossyrob/phased-agent-workflow/tree/main/skills/paw-review-understanding
Command: npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-understanding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes PR changes to generate ReviewContext.md and DerivedSpec.md artifacts, enabling durable context for code reviews and baseline derivation.

Core Features & Use Cases

  • PR context generation: Collects metadata and file changes to build a centralized ReviewContext.md.
  • Baseline research support: Initiates ResearchQuestions.md and CodeResearch.md to anchor baseline understanding.
  • Specification derivation: Produces DerivedSpec.md from PR description, diffs, and discovered context for traceable decisions.
  • Use Case: When a PR is opened, run this Skill to generate ready-to-use context and specs for review and planning.

Quick Start

Use this skill to analyze a PR and generate ReviewContext.md, ResearchQuestions.md, and DerivedSpec.md under .paw/reviews/<PR-identifier>/.

Frequently Asked Questions about paw-review-understanding

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

FAQPage Schema
How do I generate structured context from a GitHub PR for code review?

Generating structured context from a GitHub PR involves analyzing file changes and metadata to produce a ReviewContext.md file. This Skill collects PR diffs and metadata to build a centralized review artifact under the .paw/reviews/ directory.

What is a derived specification in PR code review?

A derived specification in PR code review is a DerivedSpec.md artifact that distills PR descriptions, diffs, and discovered context into traceable decisions. It provides durable, auditable specifications to anchor the review process.

How do I identify the base commit for a PR diff?

Identifying the base commit for a PR diff uses the git merge-base command to find the common ancestor. This Skill automatically relies on merge-base to determine the baseline commit for analyzing PR changes.

Can I use git diffs instead of the GitHub API to analyze PR changes?

Yes, you can use git diffs instead of the GitHub API to analyze PR changes. This Skill relies on PR metadata from either the GitHub API or git diffs to generate the review context and derived specifications.

How do I resume baseline research after gathering initial PR context?

Resuming baseline research after gathering initial PR context adapts to existing artifact states. This Skill supports resumption after baseline research by updating ResearchQuestions.md and CodeResearch.md artifacts.

What artifacts are generated when analyzing PR changes for review?

Analyzing PR changes generates ReviewContext.md, ResearchQuestions.md, CodeResearch.md, and DerivedSpec.md artifacts. These files are stored under the .paw/reviews/<PR-identifier>/ path for durable context and auditing.