write-pr-description

write-pr-description is a skill for Codex from ShivaeDev/pardes. It costs 41 tokens per session (264 once invoked), scanned A, original, MIT.

A pull-request writing guide for explaining why a change exists, how it works, and which parts deserve review. A pull request is a request for others to inspect and merge code changes.

In plain words
What is it for?
Use it to create or rewrite a pull-request title and description with sections for motivation, approach, decisions, and review callouts.
Why use it?
It gives reviewers the important context quickly without invented reasons, file lists, or unnecessary change narration.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to create or rewrite a pull-request title and description with sections for motivation, approach, decisions, and review callouts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shivaedev/pardes/write-pr-description
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ShivaeDev/pardes --skill write-pr-description
Clone the repo
git clone --depth 1 https://github.com/ShivaeDev/pardes

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-pr-description

README.md
[![agentmods](https://agentmods.dev/badge/skills/shivaedev/pardes/write-pr-description/github.svg)](https://agentmods.dev/skills/shivaedev/pardes/write-pr-description)
Your own site
<a href="https://agentmods.dev/skills/shivaedev/pardes/write-pr-description"><img src="https://agentmods.dev/badge/skills/shivaedev/pardes/write-pr-description/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-pr-description

Your own site · 80×15
<a href="https://agentmods.dev/skills/shivaedev/pardes/write-pr-description"><img src="https://agentmods.dev/badge/skills/shivaedev/pardes/write-pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 264 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00264
Opus 5.5 $0.00016 $0.00106
Sonnet 5.5 $0.00008 $0.00053
Haiku 4.5 $0.00004 $0.00026

Measured 2mo ago against content hash e6ac4a062d38, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-pr-description scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/codex-workstreams/skills/write-pr-description/SKILL.md · 50 lines

What it actually says

Write PR Description

A reviewer should understand the change in under a minute. Pull intent from the approved PR goal, accepted commits, owner-worker report, and verifier summary. Inspect specific diff details only when needed for an accurate callout. Never fabricate motivation.

Title

Describe impact or behavior. Do not use a branch name, file path, or vague placeholder.

Body

### Why?

<1-3 sentences describing the real problem or motivation>

### How?

<1-2 sentences describing the high-level technical approach>

### Decisions

- <meaningful tradeoff, rejected alternative, or scope choice with its reason>

### Callouts

- <surface where reviewer attention is valuable>

Use N/A when Decisions or Callouts has no meaningful content. Add issue links on their own lines when relevant.

Exclude

  • file lists
  • diff narration
  • test-plan narration
  • invented intent
  • speculative risk padding

Follow a stronger repository-specific PR template when one exists.

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 50 lines · 41 tokens per session scan A e6ac4a062d38

Subscribe to this mod's changes

write-pr-description is a skill published in the GitHub repository ShivaeDev/pardes (5 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 264 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.