revise

Address GitHub PR review feedback by applying fixes and running checks.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/allan-mobley-jr/forge --skill revise-allan-mobley-jr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revise
Source: https://github.com/allan-mobley-jr/forge/tree/main/skills/revise
Command: npx skills add https://github.com/allan-mobley-jr/forge --skill revise-allan-mobley-jr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Address PR review comments on an existing branch. Reads reviewer feedback, applies fixes, runs quality checks, and pushes updates to the same PR.

Core Features & Use Cases

  • Read review comments and update the same PR branch
  • Run lint, typecheck, tests, and build checks before pushing
  • Post a revision summary and update labels on the associated issue/PR

Quick Start

Describe the reviewer feedback you want addressed and the agent will apply fixes to the PR branch.

Frequently Asked Questions about revise

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

FAQPage Schema
How do I automate fixing pull request review feedback on an existing git branch?

Automating pull request review feedback involves reading reviewer comments, applying fixes to the existing branch, running lint and tests, then pushing updates. This Skill reads CHANGES_REQUESTED PRs, merges main, and automatically applies the requested revisions.

What's the best way to run quality checks before updating a GitHub PR branch?

Running quality checks before updating a GitHub PR branch ensures code stability. This Skill automatically executes lint, typecheck, tests, and builds on the existing branch after merging main, confirming all checks pass before pushing the revision summary.

Do I need specific tools to automate addressing GitHub pull request change requests?

Addressing GitHub pull request change requests automatically requires gh, git, and pnpm installed with repository access. The Skill uses these dependencies to identify CHANGES_REQUESTED PRs, apply fixes, run checks, and update associated issue labels.

Can I update the same PR branch after merging main without losing reviewer feedback?

Updating the same PR branch after merging main while preserving feedback is supported. The Skill examines existing review comments on CHANGES_REQUESTED PRs, applies fixes to the current branch, and pushes updates without creating new pull requests.

How does posting a revision summary work when applying automated PR fixes?

Posting a revision summary when applying automated PR fixes documents the changes made. After applying fixes and passing quality checks, the Skill posts a summary of revisions to the PR and updates labels on the associated agent:done issue.

What happens if lint, typecheck, tests, or builds fail during automated PR revision?

If lint, typecheck, tests, or builds fail during automated PR revision, the Skill prevents pushing broken updates to the branch. It coordinates these quality checks sequentially after applying fixes, ensuring only passing code is pushed with the revision summary.