pstack
Subagent briefs the other pstack skills hand to their subagents. Not a task skill.
- License 许可
- MIT
- 最近更新
- 2026-10-28
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- pstack
- description
- Subagent briefs the other pstack skills hand to their subagents. Not a task skill.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档agents/comment-sicko.md2.2 KB
- 参考文档agents/poteto-agent.md1.5 KB
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
pstack support files
The other pstack skills point here. Nothing to run.
04 同仓库更多 Skills
patchbook-update
Pull upstreams into a repo that keeps its changes in a patchbook (.patchbook/), repair what broke from each change's intent, test and review, then merge and deploy only when the sync was clean or the test command passes, and otherwise ask, opening a pull request when there are commits to push. Use when a scheduled task or the user says to update a patchbook repo, or for /patchbook-update or $patchbook-update.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
verify-patchbook
Drive the patchbook CLI from this checkout in a disposable sandbox (its own git repos, store, config and a fake model) and capture a transcript as proof. Use to reproduce a patchbook bug, run an issue's repro script, or prove a change to clone, init, record, the pre-commit hook, build, status, check, sync or upstream works the way a user would see it.
unslop
Cut AI tells from any writing.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or $technical-writing, or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.