A tool that posts a compact visual explanation of a GitHub pull request as a comment. It describes the important responsibilities and runtime paths without replacing the main pull request description.

Use it only when explicitly asked to create a visual pull request comment.

It helps reviewers understand the shape of a change quickly, especially when the diff spans several components.

visual-pr — Skill for Claude Code by jellydn/my-ai-tools

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 jellydn/my-ai-tools --skill visual-pr

Clone the repo

git clone --depth 1 https://github.com/jellydn/my-ai-tools

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/jellydn/my-ai-tools/visual-pr/github.svg)](https://agentmods.dev/skills/jellydn/my-ai-tools/visual-pr)

Your own site

<a href="https://agentmods.dev/skills/jellydn/my-ai-tools/visual-pr"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/visual-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/jellydn/my-ai-tools/visual-pr"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/visual-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 697 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.00027	$0.00697
Opus 5.5	$0.00011	$0.00279
Sonnet 5.5	$0.00005	$0.00139
Haiku 4.5	$0.00003	$0.00070

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

Security

Grade A, and why

visual-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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/publish-comment.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

configs/amp/plugins/my-ai-tools-skills/skills/visual-pr/SKILL.md · 77 lines

How it starts

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

Visual PR

Post a compact visual explanation of a pull request as a comment. Do not replace or append to the pull request description.

Workflow

1. Find or create the pull request

gh pr view --json url,number,title,state,baseRefName,headRefName 2>/dev/null

Use the open pull request for the current branch when one exists.
If no pull request exists, inspect the branch, commit task changes when needed, push it, and create a draft pull request according to the repository's conventions. Do not use the visual outline as the pull request body.
Ask the user to select a pull request only when the current branch has no relevant work and there is no safe pull request to create.

2. Understand the change

Read the ticket and relevant task artifacts.
Read the complete pull request diff and enough surrounding code to understand behavior and ownership.
Use gh pr view to collect metadata and changed files.
Identify only the contracts, responsibilities, and runtime paths that a reviewer needs to understand.

3. Write the visual outline

Read $SKILL_PATH/references/comment-template.md, then write the completed comment to a temporary file:

COMMENT_FILE=$(mktemp "${TMPDIR:-/tmp}/visual-pr-comment.XXXXXX")

Keep the outline concise:

Explain Why the change in exactly one sentence.
Put only reviewer warnings, migrations, compatibility constraints, deliberate omissions, or surprising decisions in Special things to note. Use - None. when there are none.
Make Change outline a structural view, not prose or a file-by-file changelog.
Use one to three focused views: a data or API shape, pseudocode, a shallow file tree, a component tree, or a call, control, or data flow.
Prefer diff blocks for changes to an existing shape. Show the complete target shape when most of it is new.
Use real names from the diff and omit categories that did not change.

4. Publish and verify the comment

COMMENT_URL=$("$SKILL_PATH/scripts/publish-comment.sh" <number> "$COMMENT_FILE")
test -n "$COMMENT_URL"
printf '%s\n' "$COMMENT_URL"
rm -f "$COMMENT_FILE"

Read the full file on GitHub · 77 lines

Files

What ships with it

2 files 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.

10d ago First seen · 77 lines · 27 tokens per session scan A 3e9cd3da4ca4

Subscribe to this mod's changes

visual-pr is a skill published in the GitHub repository jellydn/my-ai-tools (123 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 697 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-10-07.

Claude Code Code review Git and workflow amp codex open-code skills

check

Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.

tw93/Waza · 41 tokens

antfu-create-pr

Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.

antfu/skills · 54 tokens

factory-babysit-pr

Experimental workflow for babysitting one explicitly authorized pull or merge request. Use to monitor its live review state and checks, fix actionable in-scope findings, and apply separate reply, approval, merge, and soak gates.

BuilderIO/skills · 50 tokens

factory-review-prs

Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.

BuilderIO/skills · 30 tokens

comet-github-pr-review

A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.

rpamis/comet · 69 tokens

pr-description-writer

Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…

mohitagw15856/pm-claude-skills · 80 tokens