Menü
Build a linear walkthrough document explaining how a codebase or subsystem works, using Showboat with real command output for every code snippet. Use to get up to speed on unfamiliar or vibe-coded code.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Run the compound engineering step — a short retrospective after a piece of work that folds what was learned back into CLAUDE.md, the skills, or the hoard. Use at the end of every significant task.
Sort out git messes and perform history surgery — undo/rewrite commits, resolve conflicted merges and rebases, recover lost code via reflog, find regressions with git bisect.
Save a newly-figured-out trick as a minimal working example in hoard/, so future sessions can reuse or recombine it. Use after solving something non-obvious for the first time.
Build a self-contained interactive or animated HTML page that explains how an algorithm or piece of code works. Use to pay down cognitive debt when a written explanation isn't enough.
Manually exercise code beyond the automated tests — python -c for libraries, curl for APIs, browser automation with screenshots for web UIs — and document the results. Use after tests pass, before declaring work done.
Pre-pull-request checklist — verify the code works, the diff is reviewable, and the PR carries context and evidence of testing. Run before opening any pull request.
| name | walkthrough |
| description | Build a linear walkthrough document explaining how a codebase or subsystem works, using Showboat with real command output for every code snippet. Use to get up to speed on unfamiliar or vibe-coded code. |
Produce a structured, readable walkthrough that explains how the code works in detail — for onboarding, for code you've forgotten, or for vibe-coded projects you never actually read.
uvx showboat --help to learn the tool.walkthrough.md (in the repo root, or notes/ for partial ones) and
build the walkthrough in it:
showboat note for the explanatory commentary between snippets.showboat exec with sed, grep, cat, etc. to include the code
snippets you discuss. Never copy code into the document by hand — going
through exec guarantees the snippets match the real source and can't be
hallucinated.The result should teach a competent developer how the whole thing works from a single linear read.