[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV75HB14HT6PYZ1P2N8AKX":3,"skill-same:01M7EV75HB14HT6PYZ1P2N8AKX":64},{"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":31,"updatedAt":32,"install":33,"resources":45},"01M7EV75HB14HT6PYZ1P2N8AKX","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.","shreshthkapai\u002Fagent-workflows","shreshthkapai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F73650860?v=4","01M7EV5VN4GMWQ8R39WQ7KYFZQ","Shreshth","01M7EV5VNTDGPW78K42W4TYBAJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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, one per entry in the `interrogate_reviewers` role in `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml`, labeled Reviewer A, B, and so on to match the entry count. Resolve the entries with `aw-run --resolve interrogate_reviewers`. The shipped registry lists one `claude` and one `codex` entry.\n\nEach reviewer is a general-purpose, read-only subagent on its entry's model, spawned per the Subagents section of the **workflow** skill (`aw-run interrogate_reviewers --index \u003Cn> --read-only` for an entry on the other provider). An `inherit` entry runs that reviewer on the parent model.\n\nIf the spawn or `aw-run` rejects an entry's model or its provider is unavailable, run that reviewer on the model's `fallback` and say so. Families are providers, so a fallback onto the other reviewer's provider leaves the panel single-family. Report that. Do not block the review on the model issue. Never treat an `inherit` entry as a rejected model or apply the 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 and fast or standard speed for the job, per the Subagents section of the **workflow** 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, one per entry in the `interrogate_reviewers` role in `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml`, labeled Reviewer A, B, and so on to match the entry count. Resolve the entries with `aw-run --resolve interrogate_reviewers`. The shipped registry lists one `claude` and one `codex` entry.\n\nEach reviewer is a general-purpose, read-only subagent on its entry's model, spawned per the Subagents section of the **workflow** skill (`aw-run interrogate_reviewers --index \u003Cn> --read-only` for an entry on the other provider). An `inherit` entry runs that reviewer on the parent model.\n\nIf the spawn or `aw-run` rejects an entry's model or its provider is unavailable, run that reviewer on the model's `fallback` and say so. Families are providers, so a fallback onto the other reviewer's provider leaves the panel single-family. Report that. Do not block the review on the model issue. Never treat an `inherit` entry as a rejected model or apply the 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 and fast or standard speed for the job, per the Subagents section of the **workflow** 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","cafd398384400c1a0ce1da059a134394f28a690e","skills\u002Finterrogate","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows","https:\u002F\u002Fgithub.com\u002Fshreshthkapai","https:\u002F\u002Fshreshth-personal-website.vercel.app\u002F","Lost....in neural networks","2026-10-30 08:24:11",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shreshthkapai\u002Fagent-workflows --skill interrogate",{"tool":39,"command":40},"bunx","bunx skills add shreshthkapai\u002Fagent-workflows --skill interrogate",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shreshthkapai\u002Fagent-workflows --skill interrogate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002FSKILL.md",[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fcode-quality-review.md","REFERENCE","参考文档",5217,"https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002Freferences\u002Fcode-quality-review.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Flead-judgment.md",3465,"https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002Freferences\u002Flead-judgment.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Freviewer-prompt.md",2275,"https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002Freferences\u002Freviewer-prompt.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Frubric.md",4772,"https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002Freferences\u002Frubric.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7EVBMVS4ZXTSPK19XNMYNT5","workflow","Concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work, with each task routed to a playbook. Use for \u002Fworkflow, or for requests to work in this style. `aw skills always workflow` loads it into every session.","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EVBEEEVNYKRCGBH6V5SSFA","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\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7EVBBK5G5QKHXWVYHTRKJ0B","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7EVB9ED5F0RVKN70D2ZKV9W","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7EVB568STK9X05C00C83KBD","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\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7EVB0H4V10C6GQHXX4599Y2","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\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]