pstack-interrogate
Challenge a change or design through independent review; retain only findings proved by executable evidence.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pstack-interrogate
- description
- Challenge a change or design through independent review; retain only findings proved by executable evidence.
02 资源文件 1
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
Interrogate
Adversaries try to break a change or a design. A finding survives only when a run proves it. Report the findings. Do not apply fixes.
Frame
The scope is what the user names. Otherwise it is the branch diff from its merge base with the base branch, through the working tree. State the intent with the in-your-own-words guide, from the user's message, the commits, and the PR description. Ask the user when the intent is unclear.
Fan out
Run Phase A steps 3 and 4 and Phase B of the arena guide, with four changes. Read the interrogate reviewers line in place of arena runners. Copy the scope's uncommitted changes into each worktree. Spawn each adversary as a general-purpose subagent (generalPurpose in Cursor). In place of the arena task and rationale, give each adversary the scope, the intent, and this brief:
Break this change. Prove each finding with a run against the real code, such as a failing test, a repro script, or command output that shows the wrong behavior. For a design or plan, run a prototype or probe the current tree. Keep repros in your own worktree. Report each finding with a title, the exact command, the output it printed, and the output the intent requires. Leave out anything you did not run. That covers style, naming, structure, and risks that need a future change to matter. No findings is a valid result.
Verify
Verify each finding per arena Phase F by rerunning its command. Keep a finding when the output shows the failure and the failure breaks the intent. Drop the rest. Merge findings that share a root cause.
Skip arena Phases C, D, and E. Adversaries find different failures, so the verdict keeps every verified finding, not one adversary's list.
Output
- Intent: the restatement.
- Findings: for each verified finding, the command, its output, how it breaks the intent, and the adversaries that found it. Say "no verified findings" when none survive.
- Dropped: for each adversary, the count of dropped findings and why.
04 同仓库更多 Skills
teach
Teach the user a new skill or concept, within this workspace.
stop-overthinking
Manually-invoked skill that stops overthinking and forces a short, practical decision. Use only when the user explicitly invokes stop-overthinking.
remind
Rewrite the last response simpler and shorter in plain English, prefixed with a 3-5 sentence TLDR of the conversation so far. Manual-only, invoked as /remind.
read-all-adrs
Read every ADR markdown file in the project's docs/adr/ folder so you have full context on past decisions. Use only when the user explicitly calls it.
pstack-why
Find evidence for design choices and historical constraints through relevant authorized read-only sources; distinguish facts, inferences, and gaps.
pstack-unslop
Cut AI tells from any writing.