forge-reflect-pr

Review the current PR branch for refactoring, test, and documentation gaps.

65|5|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/mgratzer/forge --skill forge-reflect-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-reflect-pr
Source: https://github.com/mgratzer/forge/tree/main/skills/forge-reflect-pr
Command: npx skills add https://github.com/mgratzer/forge --skill forge-reflect-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review the current PR branch for cleanup opportunities before finalizing, including refactoring opportunities, missing tests, and documentation updates.

Core Features & Use Cases

  • Detects refactoring opportunities and code duplication across changed files.
  • Flags missing tests and outdated or missing documentation in the PR scope.
  • Provides actionable remediation steps and guidance for improving code quality before peer review.

Quick Start

Run the forge-reflect-pr skill on your feature branch to perform a self-review before requesting peer feedback.

Frequently Asked Questions about forge-reflect-pr

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

FAQPage Schema
How do I self-review my feature branch for code quality before requesting peer feedback?

Self-review your feature branch by scanning changed files for refactoring opportunities, code duplication, missing tests, and documentation gaps to improve code quality before requesting peer feedback. This structured process surfaces cleanup needs and actionable remediation steps.

What is the best way to find missing tests and documentation gaps in my current PR?

The best way to find missing tests and documentation gaps in your PR is to analyze the branch scope for code health, test coverage, and outdated docs. This identifies cleanup opportunities and provides clear guidance for remediation before finalizing the pull request.

Can I detect refactoring opportunities and code duplication across changed files in a pull request?

Yes, you can detect refactoring opportunities and code duplication across changed files in a pull request by performing a structured self-review. This checks code consistency and flags areas needing improvement, guiding your next PR steps for better code health.

Does this self-review process work with typical feature branch workflows?

Yes, this self-review process works with typical feature branch workflows where you want a structured check before requesting peer feedback. It focuses on code quality, consistency, and clear remediation guidance for the current PR branch.

Why should I check for cleanup needs on my PR branch before finalizing?

You should check for cleanup needs on your PR branch before finalizing to identify refactoring opportunities, missing tests, and documentation updates early. This improves code health and consistency, providing actionable steps to remediate issues before peer review.

What actionable remediation steps can I get for improving code quality before peer review?

You can get actionable remediation steps for improving code quality before peer review by surfacing refactoring opportunities, missing tests, and documentation gaps on your current PR branch. This guides your next PR steps with clear cleanup directions.