agentleFS
Sign inStart free
open-telemetryopen-telemetry/semantic-conventions-genai/.github/skills/pr-description/SKILL.md

pr-description

Skill528 starsChanged 41 days agoApache-2.0View on GitHub

Write or edit concise pull request descriptions for this repository. Use whenever drafting, creating, opening, or updating a pull request, or when reviewing whether a pull request description matches its diff.

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 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 9 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

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 89 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write for maintainers who need to understand the change and why it belongs in this repository without reading a second version of the diff.

    line 8
  2. Distinctive:

    Read the complete diff against the pull request's base branch.

    line 12
  3. Very specific:

    Start from .github/PULL_REQUEST_TEMPLATE.md.

    line 13
  4. Distinctive:

    Keep checklist answers accurate.

    line 17
  5. Distinctive:

    Add a concrete example near the top only when it explains a new public convention, compatibility concern, or migration.

    line 18
  6. Distinctive:

    Treat the first draft as raw material, then shorten it.

    line 25
  7. Distinctive:

    Remove details visible from the diff, including file names and exhaustive lists of attributes.

    line 27
  8. Distinctive:

    Remove chronological narration, review history, and arguments already settled in a linked issue.

    line 28
  9. Distinctive:

    Remove repeated context across sections.

    line 29
  10. Very specific:

    Remove generic sections such as Summary, Changes, Details, Testing, and Validation.

    line 31
  11. Distinctive:

    Keep the body as short as the change allows.

    line 32
  12. Distinctive:

    Do not hard-wrap prose.

    line 33
  13. Distinctive:

    Before creating or updating the pull request:

    line 35

“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

Pull request descriptions

Write for maintainers who need to understand the change and why it belongs in this repository without reading a second version of the diff.

Drafting

  1. Read the complete diff against the pull request's base branch. Read linked issues when they explain requirements or decisions that the diff does not.
  2. Start from .github/PULL_REQUEST_TEMPLATE.md. Keep its required sections and checklist, but delete all instructional comments.
  3. Open Description with one or two short sentences that state what changes and why it matters. Do not repeat the title.
  4. In Motivation, name the user journey or decision the telemetry supports and cite relevant prior art. Do not use this section to repeat the implementation.
  5. In Prototype, point to the reference scenarios or other end-to-end evidence. Explain only gaps or constraints that a reviewer cannot infer from the diff.
  6. Keep checklist answers accurate. Do not add validation commands, a changed-files list, or extra boilerplate sections.
  7. Add a concrete example near the top only when it explains a new public convention, compatibility concern, or migration. Keep it to the smallest example that makes the behavior clear.
  8. Preserve issue-closing references, compatibility notes, risks, and design constraints that reviewers need.

For repository-only changes where a template section does not apply, use one short N/A sentence rather than inventing justification.

Compression pass

Treat the first draft as raw material, then shorten it.

  • Remove details visible from the diff, including file names and exhaustive lists of attributes.
  • Remove chronological narration, review history, and arguments already settled in a linked issue.
  • Remove repeated context across sections.
  • Replace long paragraphs with one or two sentences. Use bullets only for genuinely parallel facts.
  • Remove generic sections such as Summary, Changes, Details, Testing, and Validation.
  • Keep the body as short as the change allows. There is no target word count.
  • Do not hard-wrap prose.

Before creating or updating the pull request:

  1. Apply the repository's unslop skill to the complete title and body.
  2. Compare the result with the diff once more. Every sentence must help a reviewer understand the purpose, user-visible behavior, compatibility, risk, or a decision that the diff cannot explain by itself.

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