agentleFS
Sign inStart free
bt2gobt2go/claude-skills/skills/pr-description/SKILL.md

pr-description

Skill0 starsChanged 3 months agoMITView on GitHub

Use when the user is opening a pull request or asks for a PR title and body for the current branch.

94 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ao-desktop-dev, bug-triage and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • agentlab-inSkill

    ao-desktop-dev

    Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually verify AO frontend changes in the actual desktop app rather than ao preview, dev:web, or mock data.

    Also in 4 projects that use this

  • jMertaSkill

    bug-triage

    Use when the user reports a bug, regression, runtime error, failing build, or broken test and wants reproduction, diagnosis, root-cause analysis, or an authorized fix. Isolates the shared cause and verifies the smallest relevant change.

    Also in 4 projects that use this

  • saffron-healthSkill

    address-review

    Address PR review comments systematically. Use when responding to code review feedback on a pull request.

    Also in 3 projects that use this

  • NVIDIASkill

    writing-docs

    Use when adding or changing user-facing behavior or documentation in Megatron-Energon, or when creating new .py, .sh or .md files that need license headers.

    Also in 3 projects that use this

  • Sagargupta16Skill

    dependency-audit

    Audit project dependencies for security vulnerabilities, licensing issues, maintenance health, and optimization opportunities. Use it during regular security audits (monthly or quarterly); before a major release when you want to ensure the dependency tree is clean; when evaluating whether to adopt or replace a dependency; after a security advisory affects one of your dependencies; when your install times or bundle sizes have grown noticeably.

    Also in 3 projects that use this

  • PydanticSkill

    i-have-adhd

    Shape every response for an ADHD reader who reviews the work but does not do the coding — the agent does. Use whenever responding to ANY message — coding, debugging, planning, casual. Lead with the result or the decision. Surface anything needing the user's input as a structured question, never buried in prose they'll skim past. No preamble, no recap, no closers. State errors matter-of-factly. Make finished work visible. Trigger even on casual messages and even when brevity wasn't requested.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 89 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run git log --oneline <base>..HEAD and git diff <base>...HEAD --stat.

    line 13
  2. Distinctive:

    Read the full diff of the largest three files so the summary is accurate.

    line 14
  3. Distinctive:

    Write a title under 70 characters that states the outcome, not the mechanism.

    line 15
  4. Distinctive:

    Call out anything risky: migrations, config changes, deleted behaviour, new dependencies.

    line 18
  5. Distinctive:

    No marketing tone, no emoji headers, no "this PR does the following" preamble.

    line 23
  6. Distinctive:

    Do not list every file. Reviewers can read the diff.

    line 24
  7. Distinctive:

    If the branch mixes unrelated work, say it should be split.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 89 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PR description

Turn a branch into a PR a reviewer can approve without asking questions.

Procedure

  1. Find the base branch: git symbolic-ref refs/remotes/origin/HEAD or fall back to main.
  2. Run git log --oneline <base>..HEAD and git diff <base>...HEAD --stat.
  3. Read the full diff of the largest three files so the summary is accurate.
  4. Write a title under 70 characters that states the outcome, not the mechanism.
  5. Summarise the change in three to six bullets, each one reviewer relevant.
  6. List the exact commands or steps you used to verify it. If you did not verify, say so plainly.
  7. Call out anything risky: migrations, config changes, deleted behaviour, new dependencies.
  8. Link issues only when the branch name or commits contain the number.

Rules

  • No marketing tone, no emoji headers, no "this PR does the following" preamble.
  • Do not list every file. Reviewers can read the diff.
  • If the branch mixes unrelated work, say it should be split.

Output format

## Summary
- ...

## Changes
- ...

## Testing
- ...

## Risk
- ...

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free