[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0EWZF480EW7PS99AM9K0T":3,"skill-same:01M7F0EWZF480EW7PS99AM9K0T":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7F0EWZF480EW7PS99AM9K0T","interrogate",null,"Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.","irfanalimd\u002Fpstack-ports","irfanalimd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55896554?v=4","01M7F0CXJRB2KHNDXGYJDG9R65","Mohammed Irfan Ali","01M7F0CXKNYHJDNQ8RREHX0ZG0",0,"MIT","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fclaude-code\u002Fpstack\u002Fskills\u002Finterrogate\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: interrogate\ndescription: \"Use for \\\"interrogate\\\", \\\"adversarial review\\\", \\\"multi-model review\\\", \\\"challenge this\\\", \\\"stress test this code\\\", \\\"find blind spots\\\", or \\\"tear this apart\\\". Multiple LLM reviewers challenge changes from independent angles.\"\ndisable-model-invocation: true\n---\n\n# Interrogate\n\nSpawn one reviewer per configured model to adversarially review code changes. The adversarial signal comes from model diversity, not assigned personas. The deliverable is a synthesized verdict. Do NOT auto-apply changes.\n\n## Step 1, Scope\n\nIdentify what to review from context:\n\n- If the user points at specific files or a diff, use that.\n- If on a feature branch, run `git diff main...HEAD` (or the appropriate base branch) for the full changeset.\n- If the user's message references recent work, gather the relevant files.\n\nPackage the diff or file contents with any surrounding context files the reviewers need to understand the code.\n\n## Step 2, Intent\n\nBefore spawning reviewers, state the intent in one clear paragraph from the user's message, commit messages, the PR description if one exists, and the code. If you're unsure about the intent, ask the user before proceeding.\n\n## Step 3, Spawn Reviewers\n\nLaunch all reviewers in a single message with the Agent tool, one per entry on the `interrogate reviewers` line in `~\u002F.claude\u002Frules\u002Fpstack-models.md`, labeled Reviewer A, B, and so on to match the entry count. If the rule or that line is missing, use the table defaults.\n\n| Subagent | Default model |\n|----------|---------------|\n| Reviewer A | `opus-xhigh` |\n| Reviewer B | `sonnet-xhigh` |\n\nEach reviewer gets `subagent_type: \"pstack:reader-\u003Ceffort>\"` and `model: \u003Calias>` from its configured entry, or its table default when there is no configured line (`opus-xhigh` is `model: opus` on `pstack:reader-xhigh`). Omit `model` and use `pstack:reader` for an `auto` or `inherit-parent` entry, so that reviewer runs on the parent model. Run a `codex:\u003Cslug>-\u003Ceffort>` entry through `${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpstack-seat \u003Centry> read \u003Cworkdir> \u003Cprompt-file> \u003Cout-file>` with `Bash` and `run_in_background: true`, in the same message as the `Agent` calls. On a non-zero exit (3 means no `codex` CLI), run that reviewer on Reviewer B's default and say so.\n\nIf the Agent tool rejects a configured entry, run that reviewer on its family's table default and say so. Families go by prefix: `opus-*` with `fable-*`, and `sonnet-*` with `haiku-*`. A refused `haiku-*` entry runs on Reviewer B's default. With no family match, use Reviewer A's default. If it rejects a table default, spawn with the closest equivalent from the valid models in its error message (prefer the same family and reasoning tier), and open a separate PR to update the default table. Do not block the review on the model issue. Never treat an alias entry as a rejected model or apply either fallback to it.\n\nRead `references\u002Freviewer-prompt.md` and fill in the same template for every reviewer with the stated intent, the diff or file contents, the rubric from `references\u002Frubric.md`, and the code-quality lens from `references\u002Fcode-quality-review.md`. Pick each subagent's reasoning level for the job, per the Subagents section of the **poteto-mode** skill.\n\n## Step 4, Synthesize\n\nAs results come back, build a unified picture. Parse every reviewer's findings. Merge findings that describe the same issue differently, and note which models raised each one. Findings two or more models raised independently are the highest signal. Read a lone model's finding, but weight it accordingly. Note disagreements. If one model flags something and another explicitly says the opposite, that is context for the verdict.\n\n## Step 5, Lead Judgment\n\nYou are the lead reviewer, a pragmatic senior engineer, not a neutral aggregator. Read `references\u002Flead-judgment.md` for the full framework. Put every finding in one of four buckets, with the model(s) that raised it and a one-line rationale.\n\n- **Act on**. Real issues affecting correctness, security, or maintainability given the actual goals. They would block a real PR.\n- **Consider**. Legitimate, but you're not sure they outweigh the cost of addressing them now. Worth the user's attention.\n- **Noted**. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact at this stage.\n- **Dismissed**. Wrong, nitpicky, or missing context, with a brief reason.\n\n## Output Format\n\n### Intent\n> [The stated intent paragraph from Step 2]\n\n### Reviewers\n- Reviewer [label]: [model name], [N findings] (one bullet per reviewer)\n\n### Act On\n[Each: description, which models raised it, why it matters.]\n\n### Consider\n[Each: description, which models raised it, the tradeoff.]\n\n### Noted\n[Brief list.]\n\n### Dismissed\n[Each with a brief rationale.]\n\n### Agreement Map\n[Where models agreed and diverged, and what that pattern tells us.]\n","# Interrogate\n\nSpawn one reviewer per configured model to adversarially review code changes. The adversarial signal comes from model diversity, not assigned personas. The deliverable is a synthesized verdict. Do NOT auto-apply changes.\n\n## Step 1, Scope\n\nIdentify what to review from context:\n\n- If the user points at specific files or a diff, use that.\n- If on a feature branch, run `git diff main...HEAD` (or the appropriate base branch) for the full changeset.\n- If the user's message references recent work, gather the relevant files.\n\nPackage the diff or file contents with any surrounding context files the reviewers need to understand the code.\n\n## Step 2, Intent\n\nBefore spawning reviewers, state the intent in one clear paragraph from the user's message, commit messages, the PR description if one exists, and the code. If you're unsure about the intent, ask the user before proceeding.\n\n## Step 3, Spawn Reviewers\n\nLaunch all reviewers in a single message with the Agent tool, one per entry on the `interrogate reviewers` line in `~\u002F.claude\u002Frules\u002Fpstack-models.md`, labeled Reviewer A, B, and so on to match the entry count. If the rule or that line is missing, use the table defaults.\n\n| Subagent | Default model |\n|----------|---------------|\n| Reviewer A | `opus-xhigh` |\n| Reviewer B | `sonnet-xhigh` |\n\nEach reviewer gets `subagent_type: \"pstack:reader-\u003Ceffort>\"` and `model: \u003Calias>` from its configured entry, or its table default when there is no configured line (`opus-xhigh` is `model: opus` on `pstack:reader-xhigh`). Omit `model` and use `pstack:reader` for an `auto` or `inherit-parent` entry, so that reviewer runs on the parent model. Run a `codex:\u003Cslug>-\u003Ceffort>` entry through `${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpstack-seat \u003Centry> read \u003Cworkdir> \u003Cprompt-file> \u003Cout-file>` with `Bash` and `run_in_background: true`, in the same message as the `Agent` calls. On a non-zero exit (3 means no `codex` CLI), run that reviewer on Reviewer B's default and say so.\n\nIf the Agent tool rejects a configured entry, run that reviewer on its family's table default and say so. Families go by prefix: `opus-*` with `fable-*`, and `sonnet-*` with `haiku-*`. A refused `haiku-*` entry runs on Reviewer B's default. With no family match, use Reviewer A's default. If it rejects a table default, spawn with the closest equivalent from the valid models in its error message (prefer the same family and reasoning tier), and open a separate PR to update the default table. Do not block the review on the model issue. Never treat an alias entry as a rejected model or apply either fallback to it.\n\nRead `references\u002Freviewer-prompt.md` and fill in the same template for every reviewer with the stated intent, the diff or file contents, the rubric from `references\u002Frubric.md`, and the code-quality lens from `references\u002Fcode-quality-review.md`. Pick each subagent's reasoning level for the job, per the Subagents section of the **poteto-mode** skill.\n\n## Step 4, Synthesize\n\nAs results come back, build a unified picture. Parse every reviewer's findings. Merge findings that describe the same issue differently, and note which models raised each one. Findings two or more models raised independently are the highest signal. Read a lone model's finding, but weight it accordingly. Note disagreements. If one model flags something and another explicitly says the opposite, that is context for the verdict.\n\n## Step 5, Lead Judgment\n\nYou are the lead reviewer, a pragmatic senior engineer, not a neutral aggregator. Read `references\u002Flead-judgment.md` for the full framework. Put every finding in one of four buckets, with the model(s) that raised it and a one-line rationale.\n\n- **Act on**. Real issues affecting correctness, security, or maintainability given the actual goals. They would block a real PR.\n- **Consider**. Legitimate, but you're not sure they outweigh the cost of addressing them now. Worth the user's attention.\n- **Noted**. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact at this stage.\n- **Dismissed**. Wrong, nitpicky, or missing context, with a brief reason.\n\n## Output Format\n\n### Intent\n> [The stated intent paragraph from Step 2]\n\n### Reviewers\n- Reviewer [label]: [model name], [N findings] (one bullet per reviewer)\n\n### Act On\n[Each: description, which models raised it, why it matters.]\n\n### Consider\n[Each: description, which models raised it, the tradeoff.]\n\n### Noted\n[Brief list.]\n\n### Dismissed\n[Each with a brief rationale.]\n\n### Agreement Map\n[Where models agreed and diverged, and what that pattern tells us.]\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","3cf90aeb365f524d07ef38f0fb3cbad19aeecc6f","claude-code\u002Fpstack\u002Fskills\u002Finterrogate","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports","https:\u002F\u002Fgithub.com\u002Firfanalimd","irfanali.me","2026-10-17 07:04:24",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add irfanalimd\u002Fpstack-ports --skill interrogate",{"tool":38,"command":39},"bunx","bunx skills add irfanalimd\u002Fpstack-ports --skill interrogate",{"tool":41,"command":42},"pnpm","pnpm dlx skills add irfanalimd\u002Fpstack-ports --skill interrogate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fclaude-code\u002Fpstack\u002Fskills\u002Finterrogate\u002FSKILL.md",[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcode-quality-review.md","REFERENCE","参考文档",5217,"https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fclaude-code\u002Fpstack\u002Fskills\u002Finterrogate\u002Freferences\u002Fcode-quality-review.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Flead-judgment.md",2283,"https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fclaude-code\u002Fpstack\u002Fskills\u002Finterrogate\u002Freferences\u002Flead-judgment.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Freviewer-prompt.md",2275,"https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fclaude-code\u002Fpstack\u002Fskills\u002Finterrogate\u002Freferences\u002Freviewer-prompt.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Frubric.md",4772,"https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fclaude-code\u002Fpstack\u002Fskills\u002Finterrogate\u002Freferences\u002Frubric.md",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7F0ZB3XY54V5W1VACEVX58W","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.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7F0Z9GHCK4T0WPSBEBAEMB7","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7F0Z7K4GWX9DDDD13G98GBE","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7F0Z3ATKTCM4ZEFP0V8YW90","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7F0YZW6SA7BJN6WA9T58GGX","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7F0YWN310MAHQWZF0ADYADS","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]