Explain code flow, subsystem architecture, or ownership and layering. Use why for historical rationale.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# How
Answer the requested architecture or runtime question from the relevant implementation. Trace the entry point, data flow, state changes, and boundaries far enough to explain the behavior with file references.
For a narrow question, read and answer directly. Reuse context already gathered. A code edit does not by itself require an architecture walkthrough.
For a broad subsystem, delegate independent slices only when that would save time or improve coverage. Give each explorer a distinct question and file scope; use read-only access where available. The parent reconciles findings and writes the answer. A separate explainer is optional, not a required handoff.
Use configured how-role models when delegating; otherwise inherit the parent model. If delegation is unavailable, continue locally.
## Critique
When architectural critique is requested, identify concrete problems after understanding the relevant behavior. Independent critics help with consequential or contested choices; a fixed panel is unnecessary for a small question. Judge findings against the code and project constraints, not vote counts. Report actionable findings before optional context.
## References
…
The line at the top of this page pins the label git:20260907.b1269d9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1885 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
shiwenbin1617/pstack · 4 stars · license a license file GitHub does not identify · pushed 2026-09-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b4tm57oz4ztvrlkn
GET https://markdownregistry.com/api/v1/resolve?ref=shiwenbin1617/pstack/how
GET https://markdownregistry.com/api/v1/blob/b8d5b19c5a668089697004df0d9be0d3187436ca1ab693837a8616cefd83def5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
shiwenbin1617/pstack · adapters/claude-code/overrides/setup-pstack/SKILL.md · Configure which Claude Code models pstack uses per role. Use for /setup-pstack or requests to change pstack model…
shiwenbin1617/pstack · adapters/codex/overrides/setup-pstack/SKILL.md · Configure optional per-role model preferences for pstack on Codex. Use for $setup-pstack or requests to change pstack…
shiwenbin1617/pstack · automations/benny/skills/reproduce-and-fix-issues/SKILL.md · Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft…
shiwenbin1617/pstack · automations/benny/skills/setup-benny/SKILL.md · Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker…
shiwenbin1617/pstack · skills/architect/SKILL.md · Design types, interfaces, and module ownership for a requested architectural change or an unresolved design choice.
shiwenbin1617/pstack · skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
shiwenbin1617/pstack · skills/automate-me/SKILL.md · Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a…
shiwenbin1617/pstack · skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
shiwenbin1617/pstack · skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
cursor/plugins · pstack/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
cursor/plugins · harness/pstack/claude-code/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
nightly-labs/openbot · marketplace/production-catalog/bundles/pstack/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
michael-denyer/pstack-claude · plugins/pstack/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
backnotprop/pstack · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
bastani-inc/atomic · packages/workflows/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
iap/pstack-hermes · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/code-intelligence/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…