A workflow for writing pull request descriptions that follow a repository's template. A pull request is a proposed change submitted for review before it is merged.

Use it to inspect a pull request, compare its changes, and create or update its description from the project's template.

It keeps change descriptions consistent and includes the information reviewers expect.

describe-pr — Skill for Claude Code by parcadei/Continuous-Claude-v3

About the project

Continuous-Claude-v3 is a Claude Code development environment that preserves working context between sessions, coordinates specialized agents, and stores project knowledge through ledgers, handoffs, and analysis tools. It is for people using Claude Code on ongoing or complex software work. Its catalogue entries are the skills, agents, hooks, plugin, and setting that provide its workflows and orchestration.

parcadei/Continuous-Claude-v3 · 3,948 stars · on GitHub

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 parcadei/Continuous-Claude-v3 --skill describe_pr

Clone the repo

git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/describe_pr/github.svg)](https://agentmods.dev/skills/parcadei/continuous-claude-v3/describe_pr)

Your own site

<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/describe_pr"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/describe_pr/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/describe_pr"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/describe_pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,015 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.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.01015
Opus 5.5	$0.00004	$0.00406
Sonnet 5.5	$0.00002	$0.00203
Haiku 4.5	$0.00001	$0.00102

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

Security

Grade A, and why

describe-pr 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.

.claude/skills/describe_pr/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate PR Description

You are tasked with generating a comprehensive pull request description following the repository's standard template.

Steps to follow:

Read the PR description template:
- First, check if thoughts/shared/pr_description.md exists
- If it doesn't exist, inform the user they need to create a PR description template at thoughts/shared/pr_description.md
- Read the template carefully to understand all sections and requirements
Identify the PR to describe:
- Check if the current branch has an associated PR: gh pr view --json url,number,title,state 2>/dev/null
- If no PR exists for the current branch, or if on main/master, list open PRs: gh pr list --limit 10 --json number,title,headRefName,author
- Ask the user which PR they want to describe
Check for existing description:
- Check if thoughts/shared/prs/{number}_description.md already exists
- If it exists, read it and inform the user you'll be updating it
- Consider what has changed since the last description was written
Gather comprehensive PR information:
- Get the full PR diff: gh pr diff {number}
- If you get an error about no default remote repository, instruct the user to run gh repo set-default and select the appropriate repository
- Get commit history: gh pr view {number} --json commits
- Review the base branch: gh pr view {number} --json baseRefName
- Get PR metadata: gh pr view {number} --json url,title,number,state

4b. Gather reasoning history (if available):

Check if reasoning files exist: ls .git/claude/commits/*/reasoning.md 2>/dev/null
If they exist, aggregate them: bash "$CLAUDE_PROJECT_DIR/.claude/scripts/aggregate-reasoning.sh" main
This shows what approaches were tried before the final solution
Save the output for inclusion in the PR description

Analyze the changes thoroughly: (ultrathink about the code changes, their architectural implications, and potential impacts)
- Read through the entire diff carefully
- For context, read any files that are referenced but not shown in the diff
- Understand the purpose and impact of each change
- Identify user-facing changes vs internal implementation details
- Look for breaking changes or migration requirements

Read the full file on GitHub · 87 lines

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.

2mo ago First seen · 87 lines · 10 tokens per session scan A e0a875c3793c

Subscribe to this mod's changes

describe-pr is a skill published in the GitHub repository parcadei/Continuous-Claude-v3 (3,948 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 1,015 once invoked, about $0.0000 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-09-03.

Claude Code Git and workflow agents claude-code-cli claude-code-hooks claude-code-mcp claude-code-skills

describe-pr next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
describe-prparcadei/Continuous-Claude-v3	Skill	3.9k	9mo ago	MIT	A	10	Claude Code
updateme2resh/apexyard	Skill	542	yesterday	MIT	A	27	Claude Code
releaseme2resh/apexyard	Skill	542	yesterday	MIT	A	33	Claude Code
release-syncme2resh/apexyard	Skill	542	yesterday	MIT	A	35	Claude Code
approve-mergeme2resh/apexyard	Skill	542	yesterday	MIT	A	33	Claude Code
statusme2resh/apexyard	Skill	542	yesterday	MIT	A	31	Claude Code
report-apexyard-bugme2resh/apexyard	Skill	542	yesterday	MIT	A	56	Claude Code