Official agent skill

PR Description Writer

by grafana in grafana/ai-sdk

Write or rewrite pull request descriptions from a branch diff, commit range, existing PR, issue, upstream reference, specification, bug report, or review context.

OfficialApache-2.0Auto-check passedDevelopment

Install PR Description Writer

skills CLI
$ npx skills add grafana/ai-sdk --skill pr-description-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install grafana/ai-sdk pr-description-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/grafana/ai-sdk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-description-writer .claude/skills/pr-description-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-description-writer
GitHub stars
258
Token cost
~856 tokens
SKILL.md length
335 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Write or rewrite pull request descriptions from a branch diff, commit range, existing PR, issue, upstream reference, specification, bug report, or review context.

  • Works in 8 steps: Inspect the available context → Group changes by reviewer-relevant… → For each group, explain → …
  • An agent needs to create
  • SKILL.md covers Workflow, Structure and Quality Bar
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

PR Description Writer is an agent skill from grafana/ai-sdk, published by the product's own GitHub organization. Write or rewrite pull request descriptions from a branch diff, commit range, existing PR, issue, upstream reference, specification, bug report, or review context. Use when an agent needs to create, update, or improve a PR body so it explains concrete code and behavior changes, why they were made, validation performed, and remaining risk.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests and QA and bug reports. The repository describes itself as: Grafana AI SDK for Go — streaming, tool-calling AI backends that speak fluent @ai-sdk/react. The licence is Apache-2.0.

When your agent uses it

  • An agent needs to create
  • Improve a PR body so it explains concrete code and behavior changes
  • Why they were made
  • Validation performed

Example prompts

  • “/pr-description-writer”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Inspect the available context
  2. Group changes by reviewer-relevant behavior or subsystem. Prefer categories
  3. For each group, explain
  4. Reference upstream/source context when it materially explains the change
  5. Separate generated or mechanical updates from semantic changes. Generated
  6. Include validation commands actually run. Do not imply checks passed if they
  7. Include residual risk, accepted deviations, skipped tests, or follow-up work
  8. Keep the result concise enough for reviewers to scan. Prefer precise bullets

What it can do on your machine

Read from SKILL.md and the folder at commit bb0cacc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR Description Writer loads about 856 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 335 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~856

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from grafana/ai-sdk at commit bb0cacc, republished under its Apache-2.0 licence (© grafana). 335 words, ~856 tokens.

Download SKILL.mdSave it as .claude/skills/pr-description-writer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pr-description-writer
description
Write or rewrite pull request descriptions from a branch diff, commit range, existing PR, issue, upstream reference, specification, bug report, or review context. Use when an agent needs to create, update, or improve a PR body so it explains concrete code and behavior changes, why they were made, validation performed, and remaining risk.

PR Description Writer

Use this skill to produce PR descriptions that help reviewers understand what changed and why. The description must explain concrete behavior and code changes, not just list touched files, dependencies, generated artifacts, or snapshot churn.

Workflow

  1. Inspect the available context:
    • current diff, branch range, or PR diff
    • commit list and commit messages
    • existing PR body, issue, bug report, spec, design doc, or upstream source
    • validation commands and residual risks
  2. Group changes by reviewer-relevant behavior or subsystem. Prefer categories such as API behavior, provider conversion, stream/wire format, UI behavior, persistence, docs/examples, tests/fixtures, or tooling.
  3. For each group, explain:
    • what changed in code or behavior
    • why the change was needed
    • what evidence or reference supports it
  4. Reference upstream/source context when it materially explains the change: upstream implementation, tests, release notes, specs, issues, review comments, or conformance fixtures. Mention references next to the relevant change, not only in a generic footer.
  5. Separate generated or mechanical updates from semantic changes. Generated snapshots, lockfiles, schema output, or formatter churn should support the behavioral explanation, not replace it.
  6. Include validation commands actually run. Do not imply checks passed if they did not run.
  7. Include residual risk, accepted deviations, skipped tests, or follow-up work when relevant.
  8. Keep the result concise enough for reviewers to scan. Prefer precise bullets over broad prose.

Structure

Use this structure by default and omit sections that do not apply:

markdown
## Summary

- One to four bullets describing the outcome in reviewer-facing terms.
- Include the main code/behavior changes, not only version or dependency bumps.

## Code Changes

- Area: concrete change, reason, and reference when useful.
- Area: concrete change, reason, and reference when useful.

## Tests And Fixtures

- What tests, fixtures, snapshots, or generated artifacts changed and what they
  prove.

## Validation

- `command`
- `command`

## Residual Risk

- Accepted gaps, intentional deviations, skipped fixtures/tests, blockers, or
  follow-ups.

For small PRs, merge Code Changes and Tests And Fixtures into Summary. For release, parity, migration, or generated-heavy PRs, keep the sections separate so reviewers can distinguish behavior from generated output.

Quality Bar

  • Avoid vague bullets like "updates provider code" or "regenerates snapshots" unless followed by the behavior that changed.
  • Avoid file-by-file summaries unless each file maps cleanly to a reviewer concern.
  • Do not describe unrelated opportunities discovered during review as PR scope.
  • Do not overstate certainty. Use "documents residual risk" or "leaves follow-up" when behavior remains intentionally incomplete.
  • Preserve conventional PR titles and repository-specific PR norms.

© grafana, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/pr-description-writer of grafana/ai-sdk.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit bb0cacc

Compare with similar skills

PR Description Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Description Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Description Writer this skillgrafana/ai-sdk258—~856Automated safety check: PassApache-2.0
Community Triageroryeckel/wyoming_openai219—~2.9kAutomated safety check: PassApache-2.0
Handsontable Demo Page Generatorhandsontable/handsontable22k—~1.8kAutomated safety check: PassCustom licence
Moai Workflow Testingmodu-ai/moai-adk1.2k—~2.7kAutomated safety check: PassApache-2.0
Opensource Contributionsmagnus919/hermes-profiles289—~1.4kAutomated safety check: PassMIT
cmux Screenshot and Recordingmanaflow-ai/cmux28k—~992Automated safety check: PassCustom licence

Similar skills

  • Community Triage

    roryeckel/wyoming_openai

    GitHub issues, pull requests, bug reports, scope questions, and support threads.

    219 GitHub stars~2.9k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Handsontable Demo Page Generator

    handsontable/handsontable

    Builds two throwaway HTML test pages for a Handsontable pull request, one on the released CDN version and one on the local build, to compare behavior side by side.

    22k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Moai Workflow Testing

    modu-ai/moai-adk

    A skill your agent uses when writing tests, measuring coverage, or running characterization, performance, or PR-review QA.

    1.2k GitHub stars~2.7k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Opensource Contributions

    magnus919/hermes-profiles

    Make good open source contributions — check CONTRIBUTING.md first, follow project norms, be a good citizen.

    289 GitHub stars~1.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • Captures PNG or JPEG screenshots and MP4 or GIF clips of cmux windows from the command line, as visual evidence for pull requests and bug reports.

    28k GitHub stars~992 tokensUpdated today
    Testing & QAAuto-check passed
  • Playwright Screen Recording

    liaohch3/claude-tap

    Records headless Playwright sessions as .webm videos to show a bug fix working or to give pull request reviewers visual evidence.

    3.3k GitHub stars~714 tokensUpdated today
    Testing & QAAuto-check passed

More from grafana/ai-sdk

  • Official

    Archive a completed OpenSpec change in the experimental workflow.

    258 GitHub starsUsed in 7 repos~4.1k tokens
    Auto-check passed
  • Openspec Explore

    grafana/ai-sdk

    Official

    Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec.

    258 GitHub starsUsed in 7 repos~5.7k tokens
    Auto-check passed
  • Openspec Sync Specs

    grafana/ai-sdk

    Official

    Sync delta specs from an OpenSpec change to main specs. An agent skill from grafana/ai-sdk.

    258 GitHub starsUsed in 7 repos~3.9k tokens
    Auto-check passed
  • Official

    Verify implementation matches OpenSpec change artifacts. An agent skill from grafana/ai-sdk.

    258 GitHub starsUsed in 3 repos~4.6k tokens
    Auto-check passed
  • AI SDK Parity Review

    grafana/ai-sdk

    Official

    Review an ai-sdk diff, feature, bug or package against its upstream parity contract.

    258 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • AI SDK Parity Upgrade

    grafana/ai-sdk

    Official

    Upgrade the pinned upstream AI SDK reference, assess the current Go implementation against it, and register parity work for independent implementation afterward.

    258 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Categories

Questions about PR Description Writer

What does PR Description Writer do?

Write or rewrite pull request descriptions from a branch diff, commit range, existing PR, issue, upstream reference, specification, bug report, or review context. PR Description Writer is an agent skill from grafana/ai-sdk, published by the product's own GitHub organization. Write or rewrite pull request descriptions from a branch diff, commit range, existing PR, issue, upstream reference, specification, bug report, or review context.

When should I use PR Description Writer?

PR Description Writer fits situations like: an agent needs to create; improve a PR body so it explains concrete code and behavior changes; why they were made; validation performed.

How do I install PR Description Writer in Claude Code?

Run `npx skills add grafana/ai-sdk --skill pr-description-writer -a claude-code`. Or copy the skill folder (.agents/skills/pr-description-writer in grafana/ai-sdk) into .claude/skills/pr-description-writer in your project. Claude Code loads it when a task matches its description.

How do I install PR Description Writer in Codex?

Run `npx skills add grafana/ai-sdk --skill pr-description-writer -a codex`. Or copy the skill folder (.agents/skills/pr-description-writer in grafana/ai-sdk) into .agents/skills/pr-description-writer in your project. Codex loads it when a task matches its description.

Can I use PR Description Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add grafana/ai-sdk --skill pr-description-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-description-writer, .gemini/skills/pr-description-writer, .github/skills/pr-description-writer and .opencode/skills/pr-description-writer in your project.

What does PR Description Writer need to run?

SKILL.md names no scripts, command-line tools or credentials: PR Description Writer is instructions for the agent only.

Does PR Description Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is PR Description Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR Description Writer use?

PR Description Writer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Description Writer use?

About 856 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Description Writer?

Skills that share tags, products or a category with PR Description Writer: Community Triage (roryeckel/wyoming_openai, 219 stars), Handsontable Demo Page Generator (handsontable/handsontable, 22k stars), Moai Workflow Testing (modu-ai/moai-adk, 1.2k stars) and Opensource Contributions (magnus919/hermes-profiles, 289 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Description Writer?

grafana (a GitHub organization, an official publisher) maintains it in grafana/ai-sdk, which has 258 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.

Source: grafana/ai-sdk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.