What is validate-pr-description?

A pull-request checker for validating the title, description, linked issue references, and required template sections before submission.

Use it to check conventional commit titles, issue-closing keywords, required PR sections, and an optional validation script.

It catches formatting and traceability problems that can delay review or prevent an issue from being closed automatically after merging.

validate-pr-description — Command for Claude Code by rjmurillo

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/rjmurillo/ai-agents

agentmods

npx agentmods add commands/rjmurillo/ai-agents/validate-pr-description

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/commands/rjmurillo/ai-agents/validate-pr-description/github.svg)](https://agentmods.dev/commands/rjmurillo/ai-agents/validate-pr-description)

Your own site

<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/validate-pr-description"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/validate-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/validate-pr-description"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/validate-pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 372 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.00022	$0.00372
Opus 5.5	$0.00009	$0.00149
Sonnet 5.5	$0.00004	$0.00074
Haiku 4.5	$0.00002	$0.00037

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

Security

Grade A, and why

validate-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 1mo 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/commands/validate-pr-description.md · 54 lines

What it actually says

Validate PR Description Command

Context

PR title: [User provides]
PR body: [User provides text or path to a file]

Your task

Validate the PR description against these standards:

1. Conventional Commit Title

Title must match <type>(<scope>)?: <description> where type is one of: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert.

2. Issue Linking Keywords

Body should contain at least one issue linking keyword: Closes #N, Fixes #N, Resolves #N (and their past-tense variants). These keywords auto-close the linked issue when the PR merges on platforms that support them (GitHub, GitLab). On other platforms (Azure DevOps, Bitbucket), they serve as traceability markers.

3. PR Template Compliance

Check that required sections are populated:

Summary (non-empty)
Changes (at least one item)
Type of Change (at least one checkbox marked)

Validation Script (optional)

If .claude/skills/github/scripts/pr/validate_pr_description.py exists, run it:

uv run python .claude/skills/github/scripts/pr/validate_pr_description.py \
  --title "[title]" \
  --body-file "[path-to-body.md]"

Otherwise, validate manually against the criteria above.

Report findings with actionable recommendations for any failures.

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.

1mo ago First seen · 54 lines · 22 tokens per session scan A a77b04b081da

Subscribe to this mod's changes

validate-pr-description is a command published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 372 once invoked, about $0.0001 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.

CI and CD Code review Commits Git and workflow agentic-ai ai-agents ai-assistant anthropic-claude automation

validate-pr-description