pi-visualize-code-changes
Pi skill: Mermaid before/after/diff diagrams that explain what a code change actually does
Package details
Install pi-visualize-code-changes from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:pi-visualize-code-changes- Package
pi-visualize-code-changes- Version
1.0.0- Published
- Jul 26, 2026
- Downloads
- not available
- Author
- blockedredemption
- License
- MIT
- Types
- skill
- Size
- 1 MB
- Dependencies
- 0 dependencies · 0 peers
Pi manifest JSON
{
"skills": [
"./skills"
],
"image": "https://raw.githubusercontent.com/BlockedPath/pi-visualize-code-changes/main/preview.png"
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
pi-visualize-code-changes

Pi skill that turns a code change into before / after / what-changed Mermaid diagrams — so reviewers see behaviour, not just hunks.
Installable as a Pi package. Works with any Agent Skills harness that loads SKILL.md.
Install (Pi)
pi install npm:pi-visualize-code-changes
# Recommended: structured lens prompts (ask_user_question)
pi install npm:@juicesharp/rpiv-ask-user-question
# or from git:
# pi install git:github.com/BlockedPath/pi-visualize-code-changes
# or local path while developing:
# pi install /Users/justin/dev/pi-visualize-code-changes
Without the ask-user extension the skill still works — it just picks a lens
itself instead of offering a short questionnaire when --lens is omitted.
Then in a Pi session:
/skill:visualize-code-changes
/skill:visualize-code-changes uncommitted
/skill:visualize-code-changes pr 42 --lens sequence
/skill:visualize-code-changes main...HEAD --focus src/auth --out docs/diagrams/auth.md
What it produces
One Markdown file (default docs/diagrams/<slug>.md) with:
- Before — how the flow worked
- After — how it works now
- What changed — merged, colour-coded diff view (added / removed / changed / same)
GitHub and GitLab render the Mermaid blocks natively.
Arguments
[scope] [--lens TYPE] [--focus PATH]... [--out PATH] [--slug NAME] [--render]
| Token | Meaning |
|---|---|
scope |
uncommitted, staged, pr <n>, branch <name>, main...HEAD, <sha>, … |
--lens |
control-flow, dependency, sequence, state, data-flow |
--focus |
Limit deep-read/diagram to path(s) |
--out / --slug |
Output path control |
--render |
Also emit SVGs (needs mermaid-cli) |
Requirements
No npm runtime dependencies — this package is a skill (Markdown + one stdlib Python script).
| Need | Required? |
|---|---|
| Pi (or another Agent Skills host) | Yes |
| Git | Typical — diff discovery (git diff, git show, ranges). Session-edited files still work without it |
@juicesharp/rpiv-ask-user-question (or any host tool that exposes ask_user_question / AskUserQuestion) |
Recommended — interactive lens choice when --lens is omitted. Without it, the skill auto-picks |
| Python 3 | For diagram validation only (stdlib; no pip deps) |
gh (GitHub CLI) |
Only for pr <n> scope (gh pr diff). Other scopes use git alone |
@mermaid-js/mermaid-cli (mmdc) + Chrome/Chromium |
Optional — authoritative validation and --render SVGs. Without it, validation falls back to built-in heuristics |
# recommended — lens questionnaire
pi install npm:@juicesharp/rpiv-ask-user-question
# optional — PR scope
# brew install gh # or see https://cli.github.com/
# optional but recommended — stronger Mermaid validation / SVG render
npm i -g @mermaid-js/mermaid-cli
# mmdc needs a Chrome/Chromium on PATH (or Puppeteer's bundled browser)
Package layout
pi-visualize-code-changes/
├── package.json # pi.skills → ./skills
└── skills/
└── visualize-code-changes/
├── SKILL.md
├── assets/template.md
├── references/
└── scripts/validate_mermaid.py
Development
# try without publishing
pi install /absolute/path/to/pi-visualize-code-changes
# or one-shot
pi -e /absolute/path/to/pi-visualize-code-changes
License
MIT
