القائمة
explain-diff: explain a code change, diff, branch, or PR as a rich self-contained HTML page. Flags: --target <branch>, --pr <n>, --staged, --unstaged, --output <path>.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | explain-diff |
| description | explain-diff: explain a code change, diff, branch, or PR as a rich self-contained HTML page. Flags: --target <branch>, --pr <n>, --staged, --unstaged, --output <path>. |
Produce one teaching artifact: a long-page HTML file with Background,
Intuition, Code, and Quiz. Not a PR description (make-pr) and not inline chat
prose—the reader opens the file in a browser.
| Flag | Effect |
|---|---|
--target <branch> | Branch diff: git diff <branch>...HEAD. Default: main. |
--pr <n|url> | PR diff via gh pr diff (and PR title/body for context). |
--staged | git diff --cached only. |
--unstaged | git diff only. |
--output <path> | Write path. Default: /tmp/YYYY-MM-DD-explain-<slug>.html |
Diff source is mutually exclusive. Use the first detected among --pr, --staged,
--unstaged; otherwise --target. --pr without a number when not on a PR
branch: try gh pr view to resolve; if it returns no PR, stop and ask.
Slug: short kebab from the change topic (e.g. rate-limit-api).
Collect diff text and identifiers (files, commits, PR number). If the diff is empty, stop: "No changes found to explain."
For --target, also run git log <target>..HEAD --oneline for narrative context.
Read surrounding code beyond the diff hunk lines—callers, types, tests, config—so Background can stand alone for a beginner and still narrow to what this change touches. Done when you can name the system before/after without guessing.
Follow section rubrics, prose tone, diagram families, and quiz rules in
./REFERENCE.md. Order on the page: Background → Intuition → Code → Quiz.
Trace rule: claims about the change trace to diff hunks; claims about the surrounding system trace to code read in Step 2. A sentence that traces to neither gets cut or rewritten. Completion: every Background, Intuition, and Code claim traces to a hunk or a read file.
Emit a single self-contained file: embedded CSS and JavaScript, table of
contents, section headers, one scroll (no top-level tabs). Basic responsive
layout. Apply the pre-save checklist in ./REFERENCE.md (especially pre /
white-space on code blocks).
Write only to --output or the default under /tmp/ (or another path outside
the repo). Never commit the HTML file.
Give the absolute path and a one-line open hint (open on macOS, xdg-open on
Linux, start on Windows). Do not paste the full HTML into chat.
./REFERENCE.md../REFERENCE.md.box a git repo, clone it locally and search the real source, with a tracked manifest. Delegates repo work to subagents when available, runs in the main thread otherwise. Triggers: a VCS URL (GitHub, GitLab, Bitbucket), a previously cloned repo name, or a request to clone/search/explore a repo. Flags: --persist, --update, --list, --no-subagents.
fix a Linear ticket end to end: fetch it, branch, classify mode, plan, implement, review. Flags: --base <branch> (default main), --mode <mode> (default auto; values: auto, scratch, modify, debug, trivial), and a ticket ID positional arg.
fix PR review feedback: fetch unresolved threads, triage each finding skeptically, fix what holds, reply on threads, commit and push. Triggers: /fix-pr, address PR reviews. Reached by prath-mode after make-pr. Flags: --pr <n|url>, --no-push, --no-reply.
notify the user via Discord webhook embed. Triggers: /notify, send a Discord notification, alert me when done, ping me on Discord. Flags: --task, --link, --webhook, --color, --field, --content, --dry-run.
Route a task to the right skill in prathamdby/skills and run multi-step workflow chains. Verifies the leaf skill is installed before invoking it.
make a pull request with a plain-English title and a clean-room thematic summary built from the branch diff. Triggers: open a PR, create a pull request, submit a PR. Flags: --target <branch> (default main), --ticket <id> (prefix title with the ticket), --conventional (conventional-commit title).