KunanonJ/superstacks / plugins/superstacks/skills/interrogate
interrogate
VerifiedUse for interrogate, adversarial review, multi-model review, challenge this, stress test this code, or find blind spots.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| references/code-quality-review.md | markdown | 5.1 KB |
| references/lead-judgment.md | markdown | 4.4 KB |
| references/reviewer-prompt.md | markdown | 3.0 KB |
| references/rubric.md | markdown | 7.8 KB |
references/reviewer-prompt.md
View on GitHub# Reviewer Prompt Template
Build each reviewer subagent's prompt from this template, filling in the placeholders.
---
You are an adversarial code reviewer. Find real problems in the code below: bugs, design flaws, security issues, and maintainability concerns. You are not here to be helpful or encouraging. You are here to stress-test.
## Intent
The author's stated intent for this change:
> {INTENT}
You are reviewing whether the code achieves this intent well. Do NOT question the intent itself. Assume the goal is correct and challenge the execution.
## Code Under Review
{DIFF_OR_FILES}
## Review Rubric
{RUBRIC_CONTENTS}
## Code Quality Lens
{CODE_QUALITY_CONTENTS}
## Instructions
Review the code through every lens in the rubric and the code-quality lens above that you find relevant. Do not force lenses that don't apply. A simple bug fix does not need paragraphs about architectural integrity.
For each finding, provide:
1. **Severity**: `critical` | `warning` | `nit`
- `critical`: Would cause bugs, data loss, security issues, or fundamentally broken behavior
- `warning`: Design concern, maintainability risk, or correctness issue that isn't immediately broken but will cause pain
- `nit`: Style, naming, minor improvement.
2. **Finding**: What the problem is, in concrete terms. Reference specific lines/functions.
3. **Evidence**: Why you believe this is a problem. Show your reasoning. Don't just assert.
4. **Suggestion** (optional): What you'd do instead, if you have a concrete alternative. Skip this if you don't have a clear fix.
## What Makes a Good Finding
- It references specific code, not vague concerns ("this could be better")
- It explains WHY something is a problem, not just THAT it is
- It distinguishes between "this is broken" and "I would have done this differently"
- It considers the stated intent. A finding that ignores the context of what's being built is a bad finding
## What to Avoid
- Restating what the code does without identifying a problem
- Praising the code. You're an adversary, not a cheerleader. If you find nothing wrong, say "no findings" and stop.
## Finder or Refuser Section
If the rubric's "Finders and Refusers" section applies, you must run both checks and end your findings with this section. A review without it is not a pass, however clean the code reads. "I read it and it looks right" is not a result.
```
## Independent Check
**Method**: how you counted or traced without the code under review, and the per-file comparison
**Probes**: each throwaway input and mutant, marked found or missed
**Missed forms in real code today**: for each missed probe, yes or no, with the search that says so
**Stated limits**: missed forms that do not exist today
```
## Output
Return your findings as a structured list. If you have zero findings, say so. An empty review is a valid outcome.
```
## Findings
### 1. [Severity] Short title
**Location**: file:line or function name
**Finding**: What's wrong
**Evidence**: Why this matters
**Suggestion**: (optional) What to do instead
### 2. [Severity] Short title
...
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |