pavilio-pr-explain

Generate diagram-rich markdown memos explaining pull requests and commit ranges from git diffs.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gmotyl/pavilio --skill pavilio-pr-explain-gmotyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pavilio-pr-explain
Source: https://github.com/gmotyl/pavilio/tree/main/skills/pavilio-pr-explain
Command: npx skills add https://github.com/gmotyl/pavilio --skill pavilio-pr-explain-gmotyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding what a pull request, branch, or commit range actually changed requires reading raw diffs, which is slow and hard to communicate to teammates. This Skill mechanically derives mermaid diagrams from the real diff and writes a dated, visual memo that explains the change. ## Core Features & Use Cases - Diff-grounded diagrams: Builds flowchart and sequence diagrams (always), plus class, ERD, C4, state, git-graph, gantt, and pie diagrams where the change has that dimension, all derived from real git output. - Grounding discipline: Structural diagrams must come from actual paths, symbols, commits, and line counts; any intended or future design is explicitly labelled proposed or illustrative. - Memo output: Writes to projects/<project>/memo/YYYY-MM-DD_HHmm_slug.md following panel rendering conventions, without committing or touching index files. - Use Case: After merging a feature branch, run the command to produce a visual walkthrough memo for onboarding a teammate or documenting what shipped for the team. ## Quick Start Ask the AI to explain the current branch as a diagram-rich memo by invoking /pavilio-pr-explain with an optional project name and git ref.

Frequently Asked Questions about pavilio-pr-explain

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

FAQPage Schema
How do I explain a pull request with diagrams?▼

Invoke /pavilio-pr-explain with an optional project and ref such as a branch, PR number, or commit range like main...feat/x. The skill reads the git diff and writes a dated memo with mermaid flowchart and sequence diagrams plus other diagram types where relevant.

What mermaid diagram types can document a code change?▼

Flowchart and sequence diagrams are always included for process and interaction views. Class, ERD, C4, state, git-graph, gantt, and pie diagrams are added only when the diff actually contains that dimension, such as schema changes or proportional line counts.

Can I explain uncommitted working tree changes?▼

Yes, omitting the ref argument explains the working tree or last commit. The base defaults to the merge-base with the default branch unless you specify a different comparison point.

Does the skill commit the generated memo file?▼

No, the memo is written to projects/<project>/memo/ with a timestamped slug filename but is never committed. The skill also does not modify PROJECT.md, _index.json, or any index files.

When should I not use a PR explanation memo?▼

Avoid it for explaining general concepts not tied to a specific diff, for quick unstructured notes, or for permanent architecture documentation. Those cases belong in a concept memo, a quick memo, or PROJECT.md and ADRs respectively.