Official agent skill

Writing PR Descriptions

by PostHog in PostHog/posthog

Shapes a PR body into something a reviewer understands at a glance.

OfficialCustom licenceAuto-check passedDevelopment

Install Writing PR Descriptions

skills CLI
$ npx skills add PostHog/posthog --skill writing-pr-descriptions -a claude-code

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

GitHub CLI
$ gh skill install PostHog/posthog writing-pr-descriptions --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/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-pr-descriptions .claude/skills/writing-pr-descriptions && 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
writing-pr-descriptions
GitHub stars
40k
Token cost
~5.2k tokens
SKILL.md length
3,190 words
Files
3 (incl. references)
Skills in repo
252
Repo updated
First seen
Licence
Custom licence

At a glance

Shapes a PR body into something a reviewer understands at a glance.

  • Works in 2 steps: The running app, when one is up. → Storybook, through a headless browser.…
  • Tasks that involve Pull requests
  • SKILL.md covers Pass 0: keep what the body…, Pass 1: lead with the effect, Pass 2: route each fact to a… and Pass 3: cut, plus 3 more sections
  • Calls gh and git

What it does

Writing PR Descriptions is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Shapes a PR body into something a reviewer understands at a glance. Use ALWAYS before writing or editing a PR description, before gh pr create or gh pr edit --body, and when asked to improve an existing description. Puts the effect a person sees in the first line and the mechanism under it, routes each remaining fact to the form that carries it fastest (bullet, table, diagram, screenshot, collapsed block), cuts everything a reviewer does not need, then holds what survives to a checkable shape: one fact per…

Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/examples.md` and `references/screenshots-and-reels.md`).

It sits in Development, covering Pull requests. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “Commit types”
  • “Use the writing-pr-descriptions skill to shape a PR body into something a reviewer understands at a glance”
  • “/writing-pr-descriptions”

Workflow steps

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

  1. The running app, when one is up.
  2. Storybook, through a headless browser. Use the story that covers the surface. When no story does, write a scratch story for the screenshot…

What it can do on your machine

Read from SKILL.md and the folder at commit 812e5c6. 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

    Shell commands in SKILL.md call:

    • gh
    • git

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

  • Network

    Links to these hosts (documentation or services it may open):

    • nngroup.com
    • sback.it
    • google.github.io
    • asd-ste100.org

    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

Writing PR Descriptions loads about 5.2k tokens when it runs, and up to ~9.6k if it reads all its reference files. Until then it costs about 262 tokens; SKILL.md has 3,190 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~262
When it runs · the whole SKILL.md, loaded when a task matches
~5.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.6k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,190 words (~5,229 tokens).

“A reviewer scans a description in seconds and decides where to spend attention. The body is a scanning surface, not an essay, and it has to stand without the diff. A body that narrates the code, or that would fit…”

— opening of SKILL.md by PostHog, Custom licence
name
writing-pr-descriptions

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (references) in .agents/skills/writing-pr-descriptions of PostHog/posthog.

  • SKILL.md
  • references/examples.md
  • references/screenshots-and-reels.md

Open the folder on GitHubat commit 812e5c6

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Writing PR Descriptions 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.

Writing PR Descriptions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Writing PR Descriptions this skillPostHog/posthog40k—~5.2kAutomated safety check: PassCustom licence
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from PostHog/posthog

All 252 skills in this repo
  • Authoring Log Alerts

    PostHog/posthog

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • Official

    Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).

    40k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Exploring Apm Traces

    PostHog/posthog

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    40k GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Exploring LLM Traces

    PostHog/posthog

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    40k GitHub stars~4.4k tokensUpdated today
    Auto-check passed
  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

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

Categories

Questions about Writing PR Descriptions

What does Writing PR Descriptions do?

Shapes a PR body into something a reviewer understands at a glance. Writing PR Descriptions is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Shapes a PR body into something a reviewer understands at a glance.

When should I use Writing PR Descriptions?

Writing PR Descriptions fits situations like: tasks that involve Pull requests.

How do I install Writing PR Descriptions in Claude Code?

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

How do I install Writing PR Descriptions in Codex?

Run `npx skills add PostHog/posthog --skill writing-pr-descriptions -a codex`. Or copy the skill folder (.agents/skills/writing-pr-descriptions in PostHog/posthog) into .agents/skills/writing-pr-descriptions in your project. Codex loads it when a task matches its description.

Can I use Writing PR Descriptions 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 PostHog/posthog --skill writing-pr-descriptions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-pr-descriptions, .gemini/skills/writing-pr-descriptions, .github/skills/writing-pr-descriptions and .opencode/skills/writing-pr-descriptions in your project.

What does Writing PR Descriptions need to run?

Going by SKILL.md and its folder, Writing PR Descriptions needs the command-line tools its instructions call (gh and git).

Does Writing PR Descriptions access the network?

SKILL.md names 4 domains. As links in the text: nngroup.com, sback.it, google.github.io and asd-ste100.org. This is read from the text; nothing was executed.

Is Writing PR Descriptions 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 Writing PR Descriptions use?

Writing PR Descriptions has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Writing PR Descriptions use?

About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.

What are the alternatives to Writing PR Descriptions?

Skills that share tags, products or a category with Writing PR Descriptions: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing PR Descriptions?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,200 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.

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