Agent skill

Visual PR

by jellydn in jellydn/my-ai-tools

Posts a concise visual outline as a GitHub pull request comment.

MITAuto-check passedDevelopment

Install Visual PR

skills CLI
$ npx skills add jellydn/my-ai-tools --skill visual-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jellydn/my-ai-tools visual-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/visual-pr .claude/skills/visual-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
visual-pr
GitHub stars
123
Token cost
~764 tokens
SKILL.md length
377 words
Files
3 (incl. scripts, references)
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Posts a concise visual outline as a GitHub pull request comment.

  • Works in 5 steps: Find or create the pull request → Understand the change → Write the visual outline → …
  • Explicitly asks for visual-pr
  • Runs Shell scripts from its folder; calls gh

What it does

Visual PR is an agent skill from jellydn/my-ai-tools. Posts a concise visual outline as a GitHub pull request comment. Use only when the user explicitly asks for visual-pr.

Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/comment-template.md` and `scripts/publish-comment.sh`). Compatibility notes: Requires git, jq, and the GitHub CLI (gh)

It sits in Development. It works with GitHub. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.

When your agent uses it

  • Explicitly asks for visual-pr

Example prompts

  • “Use the visual-pr skill to post a concise visual outline as a GitHub pull request comment”
  • “/visual-pr”

Requirements

  • A Bash shell
  • Compatibility (from SKILL.md): Requires git, jq, and the GitHub CLI (gh)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Find or create the pull request
  2. Understand the change
  3. Write the visual outline
  4. Publish and verify the comment
  5. Report completion

What it can do on your machine

Read from SKILL.md and the folder at commit 163951e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires git, jq, and the GitHub CLI (gh)

    From compatibility in the SKILL.md frontmatter.

Context cost

Visual PR loads about 764 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 32 tokens; SKILL.md has 377 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~764
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jellydn/my-ai-tools at commit 163951e, republished under its MIT licence (© jellydn). 377 words, ~764 tokens.

Download SKILL.mdSave it as .claude/skills/visual-pr/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
visual-pr
description
Posts a concise visual outline as a GitHub pull request comment. Use only when the user explicitly asks for visual-pr.
compatibility
Requires git, jq, and the GitHub CLI (gh)
license
MIT
user-invocable
true
disable-model-invocation
true
metadata.audience
all
metadata.workflow
git

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
bash
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:

bash
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.
Show full SKILL.md (98 more words)Show less
4. Publish and verify the comment
bash
COMMENT_URL=$("$SKILL_PATH/scripts/publish-comment.sh" <number> "$COMMENT_FILE")
test -n "$COMMENT_URL"
printf '%s\n' "$COMMENT_URL"
rm -f "$COMMENT_FILE"

The script adds a hidden visual-pr marker. It updates the current GitHub user's existing marked comment, or runs gh pr comment when none exists. Thus, one pull request has at most one visual-pr comment from that user. Never use gh pr edit for the visual outline because that replaces the pull request description.

5. Report completion

Reply with the pull request URL, the comment URL returned by GitHub, a two-sentence summary, and the verification that the comment command succeeded.

Write as one person to another. Use simple, concise language and avoid jargon.

© jellydn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts, references) in skills/visual-pr of jellydn/my-ai-tools.

  • SKILL.md
  • references/comment-template.md
  • scripts/publish-comment.sh

Open the folder on GitHubat commit 163951e

Compare with similar skills

Visual PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Visual PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Visual PR this skilljellydn/my-ai-tools123—~764Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

More from jellydn/my-ai-tools

All 35 skills in this repo
  • Babysit PR

    jellydn/my-ai-tools

    A skill your agent uses when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.

    123 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Qmd Knowledge

    jellydn/my-ai-tools

    Manage project knowledge with qmd — captures learnings, decisions, and conventions

    123 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Prd

    jellydn/my-ai-tools

    Generate Product Requirements Documents from feature ideas — plans specs and requirements

    123 GitHub starsUsed in 4 repos~1.8k tokens
    Auto-check passed
  • Capability Experiments

    jellydn/my-ai-tools

    Build an interactive report or experiment when the user asks to explore model capabilities.

    123 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • PR Review

    jellydn/my-ai-tools

    Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools.

    123 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Ralph

    jellydn/my-ai-tools

    Convert PRDs to prd.json format for the Ralph autonomous agent system

    123 GitHub starsUsed in 3 repos~1.8k tokens
    Auto-check passed

Works with

Categories

Questions about Visual PR

What does Visual PR do?

Posts a concise visual outline as a GitHub pull request comment. Visual PR is an agent skill from jellydn/my-ai-tools. Posts a concise visual outline as a GitHub pull request comment.

When should I use Visual PR?

Visual PR fits situations like: explicitly asks for visual-pr.

How do I install Visual PR in Claude Code?

Run `npx skills add jellydn/my-ai-tools --skill visual-pr -a claude-code`. Or copy the skill folder (skills/visual-pr in jellydn/my-ai-tools) into .claude/skills/visual-pr in your project. Claude Code loads it when a task matches its description.

How do I install Visual PR in Codex?

Run `npx skills add jellydn/my-ai-tools --skill visual-pr -a codex`. Or copy the skill folder (skills/visual-pr in jellydn/my-ai-tools) into .agents/skills/visual-pr in your project. Codex loads it when a task matches its description.

Can I use Visual PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jellydn/my-ai-tools --skill visual-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/visual-pr, .gemini/skills/visual-pr, .github/skills/visual-pr and .opencode/skills/visual-pr in your project.

What does Visual PR need to run?

Going by SKILL.md and its folder, Visual PR needs a shell for the scripts in its folder and the command-line tools its instructions call (gh). Our summary lists: A Bash shell. Compatibility (from SKILL.md): Requires git, jq, and the GitHub CLI (gh).

Does Visual PR access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Visual PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Visual PR use?

Visual PR is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Visual PR use?

About 764 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 287 tokens, read only when the agent opens those files.

What are the alternatives to Visual PR?

Skills that share tags, products or a category with Visual PR: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Visual PR?

jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.

Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.