Przejdź do treści
Biblioteka skilli
Programowanie · Przegląd i audyt

interrogate

/interrogate

Kilku recenzentów LLM kwestionuje zmiany z niezależnych punktów widzenia, zanim trafią do scalenia.

Repozytorium
axiom-atropos ↗
Licencja
MIT
Ostatnia zmiana repozytorium
10.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
6
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Kilku recenzentów LLM kwestionuje zmiany z niezależnych punktów widzenia, zanim trafią do scalenia.

Wyzwalacze z opisu

interrogateadversarial reviewmulti-model reviewchallenge thisstress test this codefind blind spotstear this apart
Oryginalny opis (EN)

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.

Jak działa

  1. Step 1, Scope
  2. Step 2, Intent
  3. Step 3, Spawn Reviewers
  4. Step 4, Synthesize
  5. Step 5, Lead Judgment
  6. Output Format
Sekcje z nagłówków SKILL.md, w oryginale · 72 linii, 677 słów
Podgląd SKILL.md
---
name: interrogate
description: 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.
---

Host integration: first read [HOSTS.md](../../pstack-resources/HOSTS.md); it maps the upstream workflow to the current agent host.

# Interrogate

Spawn 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.

## Step 1, Scope

Identify what to review from context:

- If the user points at specific files or a diff, use that.
- If on a feature branch, run `git diff main...HEAD` (or the appropriate base branch) for the full changeset.
- If the user's message references recent work, gather the relevant files.

Package the diff or file contents with any surrounding context files the reviewers need to understand the code.

## Step 2, Intent

Before 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.

## Step 3, Spawn Reviewers

Launch all reviewers in a single message with the Task tool, one per entry on the `interrogate reviewers` line in `~/.cursor/rules/pstack-models.mdc`, labeled Reviewer A, B, and so on to match the entry count. If the rule or that line is missing, use the table defaults.

| Subagent | Default model |
|----------|---------------|
| Reviewer A | `claude-opus-5-5-xhigh` |
| Reviewer B | `grok-4.7-xhigh-fast` |

Each reviewer gets `subagent_type: generalPurpose`, `readonly: true`, and `model` set to its configured entry, or its table default when there is no configured line. Omit `model` for an `auto` or `inherit-parent` entry, so that reviewer runs on the parent model.

If the Task tool rejects a configured entry, run that reviewer on its family's table default and say so. Families go by prefix: `claude-*`, and `grok-*` with `cursor-grok-*` and `composer-*`. A refused `composer-*` 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 slugs 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 slug issue. Never treat an alias entry as a rejected slug or apply either fallback to it.

Read `references/reviewer-prompt.md` and fill in the same template for every reviewer with the stated intent, the diff or file contents, the rubric from `references/rubric.md`, and the code-quality lens from `references/code-quality-review.md`. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **poteto-mode** skill.

## Step 4, Synthesize

As 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.

## Step 5, Lead Judgment

You are the lead reviewer, a pragmatic senior engineer, not a neutral aggregator. Read `references/lead-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.

- **Act on**. Real issues affecting correctness, security, or maintainability given the actual goals. They would block a real PR.
- **Consider**. Legitimate, but you're not sure they outweigh the cost of addressing them now. Worth the user's attention.
- **Noted**. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact at this stage.
- **Dismissed**. Wrong, nitpicky, or missing context, with a brief reason.

## Output Format

### Intent
> [The stated intent paragraph from Step 2]

### Reviewers
- Reviewer [label]: [model name], [N findings] (one bullet per reviewer)

### Act On
[Each: description, which models raised it, why it matters.]

### Consider
[Each: description, which models raised it, the tradeoff.]

### Noted
[Brief list.]

### Dismissed
[Each with a brief rationale.]

### Agreement Map
[Where models agreed and diverged, and what that pattern tells us.]
Pliki w paczce (6)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB
  • references/code-quality-review.md 5 KB
  • references/lead-judgment.md 2 KB
  • references/reviewer-prompt.md 2 KB
  • references/rubric.md 5 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · xinhi6716/axiom-atropos90MIT
hootener/brain100MIT
requie/endostack100MIT
Sup-Film/pstack-omp-lean100MIT
RIJUDEVx/agent-skills90MIT
chmonitor/chmonitor90GPL-3.0
richardochristjia/skills90MIT
chhoumann/t3-pstack90MIT
backnotprop/pstack90MIT

Migawka bazy z 13.11.2026 · wersja paczki 57070b1b7d0b (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100comms-interrogate
    Krytykuje diff równolegle z wielu perspektyw w trybie tylko do odczytu i składa uwagi recenzentów w jeden werdykt.
  • 100lie-detector
    Przeprowadza wielomodelowy przegląd adwersarialny zmian i spornych projektów przed wydaniem: kilku recenzentów na różnych modelach kwestionuje zmianę niezależnie, aby wykryć ślepe punkty i twierdzenia bez pokrycia.
  • 90mroowa-interrogate
    Przegląda zmiany w kodzie w sposób adwersarialny jednym czytelnikiem bez prawa zapisu i wnioskiem rodzica, szukając ślepych punktów.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.