What problem does it solve? Pull requests are written in code and jargon, so non-technical stakeholders cannot follow what changed, and reviewers often lack a single document that explains the change completely. This Skill turns a PR, branch, commit range, or uncommitted diff into a document a non-technical reader can follow end to end while remaining complete enough to review the change from. ## Core Features & Use Cases - Dual-layer explanation documents: Produces a full plain-English layer (opening, glossary, story, per-file summaries) plus a complete code layer with quoted before/after code, deletions, and file:line anchors. - Multiple diff targets: Explains a GitHub PR by number or URL, a branch against its merge base, a commit range, or the uncommitted working tree, using git and the gh CLI. - Verification and audits: Cross-checks PR descriptions, commit messages, and comments against the actual code, then runs two mandatory audits — readability for a layperson and completeness for a reviewer. - Use Case: A product manager needs to understand PR #60 before sign-off. Run /dilbert 60 to get a document with a ten-word glossary, the bug told as a story, and every changed function quoted before and after. ## Quick Start Ask the assistant to explain pull request number 60 as a document a non-technical reader can follow, and choose a destination folder and markdown or org format when prompted.
