pr-knowledge

Generates a verified visual HTML context page for a branch or pull request.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/unnxt30/skills --skill pr-knowledge-unnxt30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-knowledge
Source: https://github.com/unnxt30/skills/tree/main/pr-knowledge
Command: npx skills add https://github.com/unnxt30/skills --skill pr-knowledge-unnxt30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing or contributing to a pull request without understanding the pre-existing architecture leads to shallow reviews and missed regressions. This Skill maps both the diff and the fundamentals it touches, verifies every claim against source, and delivers one self-contained HTML page instead of a terminal wall of text. ## Core Features & Use Cases - Parallel codebase exploration: Dispatches read-only explorer agents per file cluster to trace fundamentals on the base branch, then the delta, with file:line citations. - Verification checkpoint: Reconciles conflicting agent claims at HEAD, verifies load-bearing numbers, and hunts classic PR pathologies like dead code, contract narrowing, and orphaned producers. - Visual HTML deliverable: Renders a single page with an anchor architecture diagram, before/after comparisons, decision log, severity-ranked hotspots, and a glossary. - Use Case: Before reviewing a teammate's large PR, run this Skill to get a verified context page showing what moved, why, and the top hotspots to scrutinize. ## Quick Start Ask the assistant to run pr-knowledge on the current branch or a specific PR number to generate the visual context page.

Frequently Asked Questions about pr-knowledge

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

FAQPage Schema
How do I get context on a pull request before reviewing it?

Run pr-knowledge with the PR number or branch name. It explores both the diff and the pre-existing code it touches, verifies claims against source, and delivers a self-contained HTML page with diagrams, a decision log, and severity-ranked review hotspots.

How to understand someone else's branch beyond the raw diff?

The Skill maps the fundamentals the branch touches, not just what it changes. Parallel explorer agents trace how the code worked on the base branch, then the delta, producing before/after comparisons and an anchor architecture diagram.

Does pr-knowledge work with GitHub pull requests?

Yes. Given a PR number, it uses gh pr view to resolve the base and head refs, then runs standard git log and git diff commands. With no input it defaults to the current branch versus the repo's main branch.

What kinds of issues does PR context analysis detect?

It hunts classic PR pathologies: responsibilities deleted with no replacement, dead code left behind, contract narrowing like dropped enum values, cross-service assumptions, and asymmetries between parallel code paths. Findings become severity-ranked hotspots.

Why might automated PR exploration reports be inaccurate?

Explorer agents can read stale mid-branch snapshots and report code that changed again by HEAD. The Skill's verification checkpoint reconciles conflicting claims with targeted reads at HEAD and marks anything unverifiable as uncertain rather than stating it as fact.