Liam ERD is a tool that turns database schemas into interactive entity-relationship diagrams, visual maps showing tables and their relationships. It helps people understand and document database structures, including complex schemas.
Borrowing it
Nothing to install: this file belongs to liam-hq/liam. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/liam-hq/liam/main/.claude/commands/update-pr-description.mdgit clone --depth 1 https://github.com/liam-hq/liamWrote 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.
[](https://agentmods.dev/commands/liam-hq/liam/update-pr-description)<a href="https://agentmods.dev/commands/liam-hq/liam/update-pr-description"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/update-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.
<a href="https://agentmods.dev/commands/liam-hq/liam/update-pr-description"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/update-pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00378 |
| Opus 5.5 | $0.00000 | $0.00151 |
| Sonnet 5.5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 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.
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
- Read the template file: Use the Read tool to get the exact content of @.github/pull_request_template.md
- Get current PR info: Use
gh pr view --json number,title,bodyto get the current PR details - Analyze the changes: Use
gh pr diffto understand what changes were made in the PR - Update the description: Use the exact template structure from step 1 and fill in appropriate content based on the PR's purpose and changes
- Apply the update: Use
gh pr editwith the properly formatted description
Common Mistakes to Avoid
- Assuming Template Content: Always read the template file - don't assume what sections exist
- Adding Non-existent Sections: Only use sections that are actually in the template
- Incomplete Descriptions: Ensure all required sections are filled with meaningful content
- 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
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 · 43 lines · 0 tokens per session scan A 3ab357beb2aa
update-pr-description is a command published in the GitHub repository liam-hq/liam (5,156 stars, last pushed yesterday), 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.
Other commands, from other repositories
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
spec-forge
Use when generating software specifications — full chain ([Idea]→[Decompose]→[PRD]→SRS→Tech Design→Review) or individual documents.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.
tdd-feature
Implement a new feature using full TDD loop.
adr-supersede
Create a new ADR that supersedes an existing one.