visual-pr
/visual-pr
Posts a concise visual outline as a GitHub pull request comment. Use only when the user explicitly asks for visual-pr.
- Author
- jellydn ↗
- Repository
- my-ai-tools ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/publish-comment.sh
What it does and when to use it
Posts a concise visual outline as a GitHub pull request comment. Use only when the user explicitly asks for visual-pr.
Original author description
Posts a concise visual outline as a GitHub pull request comment. Use only when the user explicitly asks for visual-pr.
How it works
- Workflow
SKILL.md preview
---
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."
license: MIT
compatibility: Requires git, jq, and the GitHub CLI (gh)
user-invocable: true
disable-model-invocation: true
metadata:
audience: all
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.
### 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.
Files in this package (3)
- SKILL.md 3 KB
- references/comment-template.md 1 KB
- scripts/publish-comment.sh 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jellydn/my-ai-tools | 100 | MIT |
| sovithyea/v-start | 90 | MIT |
| humanlayer/skills | 86 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version dd9fadeb1135 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100pr-write
Create or update a concise GitHub pull request for an already verified code change. Use when the user asks to open or file a PR, or invokes pr-write. Do not publish a PR when the user only asks for draft wording. - 100pr-comment-review
This skill should be used when the user asks to review a GitHub pull request AND post the findings as a comment on the PR ('review and comment on PR', 'review PR roi comment len do'). Multi-agent confidence scoring, threshold 80/100, posts via gh. For local working-tree review… - 95yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`). - 86t3-file-pr
File a concise pull request. Use when the user asks to file, open, or create a PR. - 100yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`). - 100explain-this-pr
Takes a GitHub PR URL or the current branch and writes a plain-English explanation of what it does and why, then posts it as a PR comment. Use when asked to explain a PR, summarize a pull request, write a plain-English description of a PR, add a summary comment to a PR, or…