[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7VSW62WFCJRB4CHYGQB7K":3,"skill-same:01M7A7VSW62WFCJRB4CHYGQB7K":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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7A7VSW62WFCJRB4CHYGQB7K","interrogate",null,"Use for \"interrogate\", \"adversarial review\", \"independent review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.","am-will\u002Fgooey-pi","am-will","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42459108?v=4","01M6DGTYZDSE8HR73NQBJ31689","am.will","01M7A7TJ263XAJ06M4HD6MTTJD",974,"MIT","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Finterrogate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: interrogate\ndescription: \"Use for \\\"interrogate\\\", \\\"adversarial review\\\", \\\"independent 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 independent reviewers with different review focus: correctness, security boundaries, failure recovery, and maintainability. Each inherits the current session model. Compare concrete evidence and counterexamples; agreement alone does not establish correctness.\n\nThe deliverable is a synthesized verdict. Do NOT auto-apply changes.\n\n## Step 1, Determine 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) plus any surrounding context files the reviewers need to understand the code.\n\n## Step 2, State the Intent\n\nBefore spawning reviewers, state the intent explicitly. What is this code trying to accomplish? Derive this from:\n\n- The user's message\n- Commit messages\n- PR description if one exists\n- The code itself\n\nWrite one clear paragraph. Reviewers challenge whether the work achieves the intent well, not whether the intent itself is correct. If you're unsure about the intent, ask the user before proceeding.\n\n## Step 3, Spawn Reviewers\n\nLaunch a task-appropriate panel of independent reviewers in a single message, normally two to four. Assign each a distinct focus while preserving the shared intent and rubric. Omit `model` so each reviewer inherits the current session; override only when the human explicitly chooses a model for this invocation. Do not discover or substitute another model to fill the panel.\n\n| Reviewer | Primary focus |\n|----------|---------------|\n| A | Correctness and state transitions |\n| B | Security and authorization boundaries |\n| C | Concurrency, failure recovery, and performance |\n| D | Maintainability, API contracts, and test gaps |\n\nFor each reviewer use `subagent_type: generalPurpose` and `readonly: true` where those tool options are available.\n\nRead `references\u002Freviewer-prompt.md` and fill in the template with:\n1. The stated intent\n2. The diff or file contents\n3. The review rubric from `references\u002Frubric.md`\n4. The code-quality lens from `references\u002Fcode-quality-review.md`\n\nThe same filled template goes to all reviewers, so every reviewer applies the code-quality lens.\n\nEach reviewer produces structured findings as described in the prompt template.\n\n## Step 4, Synthesize\n\nAs results come back, build a unified picture:\n\n1. **Parse all findings** from the reviewers\n2. **Identify consensus**. Findings raised by two or more reviewers independently are highest signal.\n3. **Identify single-reviewer findings**. Still worth reading, but weight accordingly.\n4. **Deduplicate**. Different reviewers may describe the same issue differently. Merge these and note which reviewers raised it.\n5. **Note disagreements**. If one reviewer flags something and another explicitly says the opposite, that's useful context for the verdict.\n\n## Step 5, Lead Judgment\n\nYou are the lead reviewer, a pragmatic senior engineer, not a neutral aggregator.\n\nRead `references\u002Flead-judgment.md` for the full framework. Reviewers only see a slice of the codebase. You have the full context (the goal, the constraints, the timeline, which tradeoffs were already considered). Use that context aggressively.\n\nCategorize every finding using these buckets:\n\n- **Act on**. Real issues affecting correctness, security, or maintainability given the actual goals. These would block a real PR.\n- **Consider**. Legitimate points, but you're not sure they outweigh the cost of addressing them right now. Worth the user's attention.\n- **Noted**. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact given the current stage.\n- **Dismissed**. Wrong, nitpicky, or missing context. Brief explanation why.\n\nFor each finding, include:\n- Which reviewer(s) raised it\n- The category (act on \u002F consider \u002F noted \u002F dismissed)\n- A one-line rationale for the categorization\n\n## Output Format\n\nPresent the verdict in this structure:\n\n### Intent\n> [The stated intent paragraph from Step 2]\n\n### Reviewers\n- Reviewer [label]: [review focus], [N findings] (one bullet per reviewer)\n\n### Act On\n[Findings that should be addressed. For each: description, which reviewers raised it, why it matters.]\n\n### Consider\n[Findings worth thinking about. For each: description, which reviewers raised it, tradeoff involved.]\n\n### Noted\n[Valid but low-priority. Brief list.]\n\n### Dismissed\n[Rejected findings with brief rationale. This shows the user what was filtered out and why, so they can override your judgment if they disagree.]\n\n### Agreement Map\n[Where did models agree, where did they diverge, and what does the pattern of agreement\u002Fdisagreement tell us?]\n","# Interrogate\n\nSpawn independent reviewers with different review focus: correctness, security boundaries, failure recovery, and maintainability. Each inherits the current session model. Compare concrete evidence and counterexamples; agreement alone does not establish correctness.\n\nThe deliverable is a synthesized verdict. Do NOT auto-apply changes.\n\n## Step 1, Determine 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) plus any surrounding context files the reviewers need to understand the code.\n\n## Step 2, State the Intent\n\nBefore spawning reviewers, state the intent explicitly. What is this code trying to accomplish? Derive this from:\n\n- The user's message\n- Commit messages\n- PR description if one exists\n- The code itself\n\nWrite one clear paragraph. Reviewers challenge whether the work achieves the intent well, not whether the intent itself is correct. If you're unsure about the intent, ask the user before proceeding.\n\n## Step 3, Spawn Reviewers\n\nLaunch a task-appropriate panel of independent reviewers in a single message, normally two to four. Assign each a distinct focus while preserving the shared intent and rubric. Omit `model` so each reviewer inherits the current session; override only when the human explicitly chooses a model for this invocation. Do not discover or substitute another model to fill the panel.\n\n| Reviewer | Primary focus |\n|----------|---------------|\n| A | Correctness and state transitions |\n| B | Security and authorization boundaries |\n| C | Concurrency, failure recovery, and performance |\n| D | Maintainability, API contracts, and test gaps |\n\nFor each reviewer use `subagent_type: generalPurpose` and `readonly: true` where those tool options are available.\n\nRead `references\u002Freviewer-prompt.md` and fill in the template with:\n1. The stated intent\n2. The diff or file contents\n3. The review rubric from `references\u002Frubric.md`\n4. The code-quality lens from `references\u002Fcode-quality-review.md`\n\nThe same filled template goes to all reviewers, so every reviewer applies the code-quality lens.\n\nEach reviewer produces structured findings as described in the prompt template.\n\n## Step 4, Synthesize\n\nAs results come back, build a unified picture:\n\n1. **Parse all findings** from the reviewers\n2. **Identify consensus**. Findings raised by two or more reviewers independently are highest signal.\n3. **Identify single-reviewer findings**. Still worth reading, but weight accordingly.\n4. **Deduplicate**. Different reviewers may describe the same issue differently. Merge these and note which reviewers raised it.\n5. **Note disagreements**. If one reviewer flags something and another explicitly says the opposite, that's useful context for the verdict.\n\n## Step 5, Lead Judgment\n\nYou are the lead reviewer, a pragmatic senior engineer, not a neutral aggregator.\n\nRead `references\u002Flead-judgment.md` for the full framework. Reviewers only see a slice of the codebase. You have the full context (the goal, the constraints, the timeline, which tradeoffs were already considered). Use that context aggressively.\n\nCategorize every finding using these buckets:\n\n- **Act on**. Real issues affecting correctness, security, or maintainability given the actual goals. These would block a real PR.\n- **Consider**. Legitimate points, but you're not sure they outweigh the cost of addressing them right now. Worth the user's attention.\n- **Noted**. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact given the current stage.\n- **Dismissed**. Wrong, nitpicky, or missing context. Brief explanation why.\n\nFor each finding, include:\n- Which reviewer(s) raised it\n- The category (act on \u002F consider \u002F noted \u002F dismissed)\n- A one-line rationale for the categorization\n\n## Output Format\n\nPresent the verdict in this structure:\n\n### Intent\n> [The stated intent paragraph from Step 2]\n\n### Reviewers\n- Reviewer [label]: [review focus], [N findings] (one bullet per reviewer)\n\n### Act On\n[Findings that should be addressed. For each: description, which reviewers raised it, why it matters.]\n\n### Consider\n[Findings worth thinking about. For each: description, which reviewers raised it, tradeoff involved.]\n\n### Noted\n[Valid but low-priority. Brief list.]\n\n### Dismissed\n[Rejected findings with brief rationale. This shows the user what was filtered out and why, so they can override your judgment if they disagree.]\n\n### Agreement Map\n[Where did models agree, where did they diverge, and what does the pattern of agreement\u002Fdisagreement tell us?]\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","f63b9cfa707488880eeb9f47984fbf383e397322",".agents\u002Fskills\u002Fpstack\u002Finterrogate",87,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi","https:\u002F\u002Fgithub.com\u002Fam-will","Context Engineer, Developer, Husband, Father","2026-10-25 13:02:03",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add am-will\u002Fgooey-pi --skill interrogate",{"tool":39,"command":40},"bunx","bunx skills add am-will\u002Fgooey-pi --skill interrogate",{"tool":42,"command":43},"pnpm","pnpm dlx skills add am-will\u002Fgooey-pi --skill interrogate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Finterrogate\u002FSKILL.md",[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fcode-quality-review.md","REFERENCE","参考文档",5372,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Finterrogate\u002Freferences\u002Fcode-quality-review.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Flead-judgment.md",3468,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Finterrogate\u002Freferences\u002Flead-judgment.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Freviewer-prompt.md",2756,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Finterrogate\u002Freferences\u002Freviewer-prompt.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Frubric.md",5096,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\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},"01M7A8040XWQF3KCYT7G12G1TA","prime-work-schedules","Create, inspect, edit, pause, resume, run, and delete durable GooeyPi scheduled tasks. Use when the user asks to schedule recurring or one-time work in the current project or thread. Use rlm-heartbeat instead for temporary internal polling while actively working.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fprime-work-schedules\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},"01M7A7ZYRC65CS56VJV4CVKWFV","prime-work-browser","Drive the GooeyPi in-app browser for this thread with the browser_* tools - open tabs, navigate, read pages, click, type, scroll, screenshot, and extract data. Use when the user asks to open, test, inspect, or interact with a website or a local dev server inside GooeyPi.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fprime-work-browser\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},"01M7A7ZV00WXP2QFC5YPDJXTNV","gooeypi-computer-use","Drive native applications on macOS, Windows, or Linux through the separately installed TryCUA driver CLI.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fgooeypi-computer-use\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},"01M7A7ZNTPXAJ17VX4MTAND91G","verify-gooeypi","Launch and drive the GooeyPi desktop (Electron) app to prove user-facing behavior — sidebar navigation, Settings, and Capabilities — capturing screenshots and ARIA snapshots. Reach for this when verifying a GooeyPi UI change or confirming the app still works end to end.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fverify-gooeypi\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},"01M7A7ZK9FBXTZC33HEAJ4C3HW","review-pr-viability","Review a pull request or issue for value, implementation quality, maintainability, regression risk, and reliance on upstream changes.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview-pr-viability\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},"01M7A7ZDK2B6KE9ZE33GS4V180","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\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Fwhy\u002FSKILL.md",[],[]]