agentleFS
Sign inStart free
PedroMosqueraPedroMosquera/squadai/.agents/skills/pr-description/SKILL.md

pr-description

Skill10 starsChanged 20 days agoMITView on GitHub

Generate pull request descriptions from diff analysis

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 82 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Analyze the diff: Read all changed files to understand the scope.

    line 13
  2. Distinctive:

    Test: Test additions or improvements.

    line 23
  3. Distinctive:

    Write the summary: Create 1-3 bullet points.

    line 26
  4. Distinctive:

    Keep each bullet to one sentence.

    line 29
  5. Distinctive:

    Keep the description concise and factual.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 82 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 Skill

Generate a clear, reviewer-friendly pull request description by analyzing the diff and commit history. Follow this protocol for consistent output.

Steps

  1. Analyze the diff: Read all changed files to understand the scope.
    • What files were added, modified, or deleted?
    • What is the primary purpose of the change?
    • Are there multiple logical changes bundled together?
  2. Identify the change type: Classify the PR.
    • Feature: New functionality or capability.
    • Fix: Bug fix or error correction.
    • Refactor: Code restructuring without behavior change.
    • Docs: Documentation updates.
    • Test: Test additions or improvements.
    • Chore: Build, CI, dependency, or tooling changes.
  3. Write the summary: Create 1-3 bullet points.
    • Focus on what changed and why, not how.
    • Lead with the most important change.
    • Keep each bullet to one sentence.
  4. List the changes: Group modifications by area.
    • Group related files together (e.g., "API endpoints", "Database models").
    • Describe what changed in each group, not file-by-file.
    • Note any new dependencies or configuration changes.
  5. Describe testing: Explain what was verified.
    • What tests were added or updated?
    • How can a reviewer verify the change manually?
    • Are there any known limitations or untested scenarios?
  6. Note breaking changes: Flag anything that affects existing behavior.
    • API changes (new required parameters, removed endpoints).
    • Database migrations or schema changes.
    • Configuration format changes.
    • Dependency version bumps with breaking changes.

Output Format

## Summary
- <1-3 bullet points describing the change>

## Changes
- <grouped description of modifications>

## Testing
- <what was tested and how to verify>

## Breaking Changes
- <list any breaking changes, or "None">

Keep the description concise and factual. Avoid subjective language. Omit the Breaking Changes section if there are none.

Download now (ZIP)

  • Other versions87 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 87

    1. jdx/mise★ 36ksame name
    2. zulip/zulip★ 26ksame name
    3. Nagi-ovo/gemini-voyager★ 21ksame name
    4. pipecat-ai/pipecat★ 17ksame name
    5. ComposioHQ/agent-orchestrator★ 14ksame name
    6. OrchestratorInc/agent-orchestrator★ 14ksame name
    7. Untrivial-ai/agent-orchestrator★ 14ksame name
    8. AgentWrapper/agent-orchestrator★ 13ksame name
    9. sanity-io/sanity★ 6.4ksame name
    10. pytorch/torchtitan★ 5.9ksame name

    77 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use ao-desktop-dev, bug-triage and 10 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

    • GitHubSkill

      commit-message

      Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help

      Also in 8 projects that use this

    • francogalfreSkill

      dependency-audit

      Audits package.json dependencies for outdated packages, security vulnerabilities, unnecessary deps, and version issues. Use when the user says "audit my dependencies", "check my packages", "what deps should I update", "clean up package.json", "are there security issues in my deps", or pastes a package.json.

      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

    • HashiCorpSkill

      changelog

      Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

      Also in 5 projects that use this

  • In this repository28 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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