agentmods.dev

update-pr-description

A command for updating a GitHub pull request (a request to merge code into a project) using the repository’s pull-request template.

In plain words
What is it for?
Use it to review a pull request, rewrite its description in English, and apply the update through GitHub’s command-line tool.
Why use it?
It prevents descriptions from missing the project’s required sections or being based on an outdated template. It uses the pull request’s actual details and code changes.

Command for Claude Code

5.1k 5d ago A scan 0 tokens original Apache-2.0
View the source file liam-hq/liam
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.

agentmods
npx agentmods add commands/liam-hq/liam/update-pr-description
Clone the repo
git clone --depth 1 https://github.com/liam-hq/liam

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 378 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00378
Opus 5 $0.00000 $0.00189
Sonnet 5 $0.00000 $0.00076
Haiku 4.5 $0.00000 $0.00038

Measured 3d ago against content hash 3ab357beb2aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-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 3d 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/update-pr-description.md · 43 lines

What it actually says

Update PR Description

description: Update a pull request description to match the project's PR template

Task

Update the specified pull request's description to follow the project's PR template format defined in @.github/pull_request_template.md.

IMPORTANT:

  • Always read the exact content of @.github/pull_request_template.md first to understand the current template structure. Do not assume the template contains sections that are not actually present.
  • Write all PR descriptions in English. This is critical for project consistency.

Steps

  1. Read the template file: Use the Read tool to get the exact content of @.github/pull_request_template.md
  2. Get current PR info: Use gh pr view --json number,title,body to get the current PR details
  3. Analyze the changes: Use gh pr diff to understand what changes were made in the PR
  4. Update the description: Use the exact template structure from step 1 and fill in appropriate content based on the PR's purpose and changes
  5. Apply the update: Use gh pr edit with the properly formatted description

Common Mistakes to Avoid

  1. Assuming Template Content: Always read the template file - don't assume what sections exist
  2. Adding Non-existent Sections: Only use sections that are actually in the template
  3. Incomplete Descriptions: Ensure all required sections are filled with meaningful content
  4. Incorrect Section Headers: Use the exact section headers from the template

Example Command Usage

# Update PR description for current PR
gh pr edit --body "$(cat <<'EOF'
[Use the exact template structure from @.github/pull_request_template.md]
EOF
)"

Arguments

$ARGUMENTS

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. 3d ago First seen · 43 lines · 0 tokens per session scan A 3ab357beb2aa

Subscribe to this mod's changes

update-pr-description is a command published in the GitHub repository liam-hq/liam (5,100 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 378 tokens. 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-30.

Git and workflowdata-visualizationdatabase-schemadocumentationdocumentation-toolentity-relationship-diagram
Related

Other commands, from other repositories

profile

Save, load, inspect, update, reset, or delete diagram-design client profiles.

cathrynlavery/diagram-design · 16 tokens

ado-pull

Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.

anton-abyzov/specweave · 23 tokens

github-push

Push local progress to GitHub Issues (like git push). Updates issue with task completion checklist.

anton-abyzov/specweave · 19 tokens

export

Export the wiki (or architecture model) to markdown, HTML, JSON, or Structurizr DSL.

repowise-dev/repowise · 21 tokens

review-teardown

Delete a review branch to free the shared Pantheon review slot.

SumoLogic/sumologic-documentation · 0 tokens

docguard.guard

Run DocGuard guard validation — check all validators and fix any issues.

raccioly/docguard · 13 tokens