pull-request

Manages the full GitHub pull request lifecycle from branch hygiene through merge gating.

4.0k|282|Updated Dec 2, 2024
One-click install
npx skills add https://github.com/basicmachines-co/basic-memory --skill pull-request-basicmachines-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/basicmachines-co/basic-memory/tree/main/.agents/skills/pull-request
Command: npx skills add https://github.com/basicmachines-co/basic-memory --skill pull-request-basicmachines-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request work often stalls or ships prematurely because descriptions are thin, review feedback is handled inconsistently, and merges happen on green CI alone. This Skill enforces a disciplined end-to-end PR workflow so nothing is merged before review loops, checks, and scope decisions are resolved. ## Core Features & Use Cases - Full PR Lifecycle Management: Covers opening, updating, describing, pushing, monitoring, reviewing, addressing comments, and merging pull requests via the GitHub CLI. - Structured PR Descriptions: Enforces a Why / What Changed / Implementation Details / Testing / Risks format so reviewers understand changes without watching the chat. - Codex Review Loop & Scope Discipline: Classifies review feedback as in-scope blocker, sidequest, or fast follow, and gates merging on explicit approval plus passing checks. - Use Case: After pushing a bugfix branch, use this Skill to write the PR body, open the PR, monitor CI and reviewer feedback, push back on out-of-scope requests with evidence, and merge only after the approval gate is satisfied. ## Quick Start Ask the agent to open a pull request for the current branch and drive it through review and merge using the pull-request workflow.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I write a good GitHub pull request description?▼

A good PR description includes Why the change is needed, What Changed, Implementation Details, Testing with exact commands and outcomes, and Risks or Follow-ups. Avoid bodies that only restate commit messages; explain the change to a reviewer who did not see the conversation.

How do I handle automated code review comments on a pull request?▼

Classify each finding as an in-scope blocker, a sidequest, or a fast follow by reproducing it against the current head. Fix genuine regressions in the current PR, push back on out-of-scope feedback with evidence, and track separable concerns as follow-up issues.

When is it safe to merge a GitHub pull request?▼

Merge only after confirming the latest head SHA, passing required checks on that head, no unaddressed review comments, and explicit reviewer approval or user override. Green CI alone is never sufficient grounds to merge.

Should every review comment be fixed in the current pull request?▼

No. Only regressions introduced by the branch or direct violations of stated behavior are in-scope blockers. Speculative hardening or unrelated cleanup should be declined with evidence, and material but separable concerns should become tracked fast-follow issues.

What tools does this pull request workflow require?▼

The workflow uses the GitHub CLI (gh) for viewing PRs, issues, review comments, and CI status, plus the repository's own validation gates such as just fast-check or just package-check. Python tooling runs through the project's virtual environment.