review-changes

Identify and summarize branch changes compared to the integration baseline.

1|Updated Sep 8, 2022
One-click install
npx skills add https://github.com/furystack/pi-rat --skill review-changes-furystack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-changes
Source: https://github.com/furystack/pi-rat/tree/main/.cursor/skills/review-changes
Command: npx skills add https://github.com/furystack/pi-rat --skill review-changes-furystack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review all changes introduced on the current branch relative to the upstream integration branch to prepare for PR review and verification.

Core Features & Use Cases

  • Detect changed files and summarize diffs to help reviewers focus on impact.
  • Coordinate subagents to perform pre-flight checks (formatting, versioning, changelog, tests) and ensure policy compliance.
  • Support branching workflows by validating that base branch recommendations (develop) are used for comparisons.

Quick Start

Provide a concise review of current branch changes by comparing it to develop and export a summary.

Frequently Asked Questions about review-changes

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

FAQPage Schema
How do I review git branch changes before a pull request?

To review git branch changes before a pull request, compare your current branch against the upstream integration baseline. This summarizes diffs and detects change types to help reviewers focus on impact and verify policy compliance.

What is the best way to summarize code diffs for PR review?

Summarizing code diffs for PR review involves identifying all changed files relative to the base branch. This process detects specific change types and coordinates subagents to validate formatting, dependencies, tests, and changelogs.

Can I automate pre-flight checks for formatting and tests on a git branch?

You can automate pre-flight checks for formatting and tests by coordinating subagents during branch review. This validates versioning, changelog updates, and test executions to ensure policy compliance before merging changes.

Does branch review work with GitHub actions and develop integration baselines?

Branch review works effectively with GitHub actions and develop integration baselines. It validates that base branch recommendations are used for comparisons, ensuring accurate diff analysis across various branching workflows.

Why should I use develop as the base branch for comparing code changes?

Using develop as the base branch for comparing code changes ensures accurate pre-flight analysis and execution strategy. It supports branching workflows by validating that upstream integration branch recommendations are correctly applied.

What limitations exist when automating pull request diff analysis?

Limitations when automating pull request diff analysis include relying entirely on the correct integration baseline for comparison. Without the proper base branch, detecting change types and validating formatting or tests may yield inaccurate impact summaries.