skills/mgratzer/forge/forge-reflect-pr

forge-reflect-pr

SKILL.md

Reflect on PR

Self-review the current PR branch before requesting peer review.

Input

No primary argument required. Operates on the current branch.

Optional last parameter: -- <additional context>

Interpret $ARGUMENTS as optional execution guidance for the review focus. If no argument is provided, use the default review checklist.

Process

Step 1: Identify Changes

DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')
git diff --name-only $DEFAULT_BRANCH...HEAD

Step 2: Review Each Changed File

For each file, check the default criteria, while prioritizing any areas called out in the optional additional context:

  1. Duplication — repeated patterns that should be extracted
  2. Function size — anything too long to follow at a glance
  3. Naming — clear and consistent
  4. Layer placement — logic in the right abstraction layer
  5. Dead code — unused imports, variables, or functions introduced
  6. Pattern consistency — if a pattern was changed, are ALL files using it updated?
    grep -rn "<changed-pattern>" src/
    

Step 3: Check Configuration

  • New env vars documented in .env.example?
  • Config placed where it's consumed?
  • External service credentials handled properly (not hardcoded)?
  • Manual deployment steps captured in PR description?

Step 4: Assess Test Coverage

Check for corresponding test files. Run coverage on changed files if supported. Focus on: error handling branches, edge cases, new public functions.

Step 5: Review Documentation

Check if changes require updates to: docs/*.md, AGENTS.md, code comments, README.

If you removed or renamed something, grep docs for stale references:

grep -rn "<removed-term>" docs/

Step 6: Cleanup

  • No console.log debugging statements
  • No commented-out code
  • No TODO comments that should be addressed now
  • No unused imports
  • No hardcoded values that should be constants

Step 7: Quality Gates

Run the project's lint, format, type check, and test commands. Fix issues.

Step 8: Report

Summarize: refactoring done, tests added, documentation updated, items deferred.

For each deferred item, create a GitHub issue — do not leave deferred improvements untracked:

gh issue create --title "<title>" --body "<context and proposed solution>"

Output Format

## PR Reflection Summary

### Refactoring
- [x/none] <what was done>

### Tests
- [x/none] <what was added>

### Documentation
- [x/none] <what was updated>

### Cleanup
- [x/none] <what was fixed>

### Deferred Items
- Created #<num>: <title> (or: None identified)

Guidelines

  • Pattern consistency is the highest-value check — a missed pattern update causes bugs across the codebase
  • Create issues for deferred items — never leave improvements as untracked notes
  • Run quality gates before reporting — catch issues before the reviewer does

Related Skills

After review: Use forge-address-pr-feedback to address reviewer feedback.

Example Usage

/forge-reflect-pr
/forge-reflect-pr -- pay extra attention to migration safety and missing regression tests
Weekly Installs
14
Repository
mgratzer/forge
GitHub Stars
61
First Seen
Feb 9, 2026
Installed on
opencode14
gemini-cli14
github-copilot14
codex14
amp14
kimi-cli13