skills.rest
lossyrob
lossyrobCOMMUNITY
Explore all skills by this author →
𝕏@lossyrobGitHub

paw-review-baseline

Generate CodeResearch.md documenting the pre-change codebase at the base commit.

39|6|Updated Oct 8, 2025
Search Tags:#baseline#PR review#code-research#artifact documentation#CodeResearch.md#git base commit
One-click install
npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-baseline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paw-review-baseline
Source: https://github.com/lossyrob/phased-agent-workflow/tree/main/skills/paw-review-baseline
Command: npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-baseline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Baseline Research Activity Skill documents how the system worked before PR changes, enabling informed review and design decisions by preserving context and patterns.

Core Features & Use Cases

  • Baseline documentation: Captures pre-change behavior, conventions, and integration points for reference during reviews.
  • Artifact generation: Creates CodeResearch.md with structured findings at the base commit.
  • Multi-repo readiness: Supports per-repo processing and cross-repo pattern identification when reviewing multiple PRs.

Quick Start

Trigger the PAW baseline research workflow for your PR to create CodeResearch.md in .paw/reviews/PR-<number>-<repo-slug>/CodeResearch.md.

Frequently Asked Questions about paw-review-baseline

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

FAQPage Schema
How do I document a pre-change codebase for PR review?▼

To document a pre-change codebase for PR review, you can baseline the repository at the git base commit to capture existing behavior, conventions, and integration points before changes are applied.

What is the best way to capture system behavior before applying PR changes?▼

Capturing system behavior before applying PR changes involves checking out the git base commit and analyzing the codebase state to preserve context, allowing for informed review and design decisions.

How do I generate CodeResearch.md with file:line references for a base commit?▼

Generating CodeResearch.md with file:line references requires analyzing the repository at the git base commit and outputting structured findings to the .paw/reviews/PR-<number>-<repo-slug>/ directory.

Can I review baseline code across multiple repositories?▼

Yes, baseline code review supports multi-repo scenarios by processing each repository's base state individually, enabling cross-repo pattern identification and per-repo context capture.

Does baseline research work for single-repo code reviews?▼

Yes, baseline research applies to single-repo reviews by checking out the base commit, restoring state, and generating artifact metadata to document how the system worked before PR changes.

When do I need to baseline a git base commit before reviewing code?▼

Baselining a git base commit is needed when you require accurate context of pre-change conventions and integration points to properly evaluate PR modifications and their impact on the existing system.

Related Skills

Explore More Software Engineering Skills→
slbugslbug
7

rb:secrets

Detect leaked secrets and exposed credentials in Ruby codebases.

Community
Intermediate
the-agency-aithe-agency-ai
39

pre-phase-review

Analyze PVR, Architecture & Design, and plan documents for accuracy and completeness.

Official
Intermediate
ascerra-fullsend-rehearsalascerra-fullsend-rehearsal

code-review

Analyze code changes for correctness, security, intent, style, and documentation compliance.

Official
Advanced
pradyumnasagarpradyumnasagar
6

roadmap-author

Guide authors through creating and validating ORS SKILL.md files.

Community
Intermediate