AGENT SKILL

pr

Create or revise a draft pull request.

License 许可
MIT
最近更新
2026-11-12
Stars
★ 2
Forks
0

01 前言 Front Matter

name
pr
description
Create or revise a draft pull request.
allowed-tools
Bash, Read, Write, Glob
argument-hint
[pr-number-to-edit]

02 资源文件 3

03 SKILL.md 正文

Pull request

Open a draft PR that tells a PM what changed for users and what it moved. Mark it ready only on request.

Template

Search the target repo's .github/, root, and docs/ for a committed template. Without one, use .github/pull_request_template.md. Keep the chosen template's headings and markers.

Body

Work out what changed from the issue, the source, the diff, and the commits. A branch name or the commit subjects alone are not enough. Write BLUF (bottom line up front): Goal's first sentence states the outcome and its measured impact, so a PM who stops there knows what the PR did. Explain behavior and decisions and leave the file list to the diff.

Summary answers the same three questions for each area the change reaches, even where the repo's template words its Summary another way. Give each area a bold lead line, then one sentence each:

  • Problem: what a user hit or could not do, in their words.
  • Cause: the mechanism that produced it. Name no files. A new capability has no cause, so drop the line.
  • Fix: the approach that solves it, so a reader knows how without opening the diff.

Keep each of those lines under 20 words. Leave fallbacks, edge cases, test counts, and file names to the diff. Keep the whole body within the template's word budget, and cut detail before cutting a section.

For visible changes, add named before/after captures, or a recording for motion and flows. Upload them as GitHub user attachments per references/github-attachments.md.

Submit

Follow references/body.md for wording and for where the body file goes. Submit with gh pr create or gh pr edit, keeping the formatting intact.

04 同仓库更多 Skills

notambourine
notambourine/agent-plugins

human-voice

Humanize prose by choosing a surgical voice edit or a structural rewrite. Use for AI-sounding drafts, anti-slop passes, editorial reviews, and requests to preserve an author's voice.

★ 2
notambourine
notambourine/agent-plugins

install-anti-slop

Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository. Use whenever a user asks to add anti-slop lint rules, copy the anti-slop plugin, configure opinionated Oxlint rules, or migrate an existing local anti-slop setup.

★ 2
notambourine
notambourine/agent-plugins

improve-codebase-architecture

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

★ 2
notambourine
notambourine/agent-plugins

eli5

Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture explainer of how something works.

★ 2
notambourine
notambourine/agent-plugins

codebase-design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

★ 2
notambourine
notambourine/agent-plugins

audit-codebase

Read-only whole-codebase audit for simplifications in data structures, state representation, control flow, algorithms, and ownership. Inventories every subsystem as a coverage contract, reviews each one in a bounded subagent, verifies each finding against the repo, then audits its own coverage. Never edits, runs tests, commits, or pushes. Use for "audit this codebase", "find simplifications", or a pre-refactor survey.

★ 2