visual-pr

Generates structured pull request descriptions with visual change outlines using GitHub CLI.

5|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/nuggocto/dotfiles --skill visual-pr-nuggocto
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: visual-pr
Source: https://github.com/nuggocto/dotfiles/tree/main/opencode/skills/visual-pr
Command: npx skills add https://github.com/nuggocto/dotfiles --skill visual-pr-nuggocto

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve? Writing clear pull request descriptions is time-consuming, and reviewers often struggle to understand why a change exists and how it is structured. This Skill automates creating or updating PR descriptions that explain the change with concise visual outlines. ## Core Features & Use Cases - Automatic PR detection: Finds the PR for the current branch via gh pr view, or creates one after committing and pushing task-related changes. - Template-driven descriptions: Writes a PR body with a one-sentence rationale, reviewer warnings, and a compact change outline using diff blocks, pseudocode, file trees, component trees, and call-flow views. - Persistent artifacts: Saves the description to .humanlayer/tasks/ and publishes it with gh pr edit, then reports the PR URL and changed files. - Use Case: After finishing a feature branch, invoke the skill to produce a reviewer-friendly PR description showing the new API contract, changed component tree, and control-flow diffs, then publish it to GitHub automatically. ## Quick Start Ask the agent to use the visual-pr skill to describe the pull request for the current branch.

Frequently Asked Questions about visual-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate a pull request description?โ–ผ

Invoke the visual-pr skill on your current branch. It checks for an existing PR with gh pr view, gathers the diff and ticket context, writes a description from its template, and publishes it with gh pr edit.

How to write a PR description that reviewers understand quickly?โ–ผ

Keep the rationale to one sentence, list at most three reviewer warnings, and show the change as visual outlines: diff blocks for modified shapes, shallow file trees, component trees, and call-flow diagrams rather than prose changelogs.

Does this skill create a PR if none exists for the branch?โ–ผ

Yes. If no PR exists, it inspects git status and branch commits, commits task-related changes when needed, pushes the branch with an upstream, and creates a PR following the repository's git safety protocol.

Where are generated PR descriptions saved?โ–ผ

Descriptions are saved to .humanlayer/tasks/{task-slug}/pr-description.md when a task directory exists, otherwise to .humanlayer/tasks/pr-{number}/description.md, before being published to the PR body.

What tools are required to run this PR description workflow?โ–ผ

The workflow requires git and the GitHub CLI (gh) for PR inspection, creation, and editing. It reads template and convention files from the skill's references directory and uses no additional package dependencies.