Comms Interrogate
Multi-reviewer critique of a diff, run as parallel read-only subagents from distinct angles, then synthesized into one verdict. Use for "interrogate", "adversarial review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".
Install
npx skills add jpoehnelt/skills --skill comms-interrogategit clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/comms-interrogate ~/.claude/skills/comms-interrogatePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Interrogate
Spawn several reviewers in parallel, each with a distinct angle, to critique a change. Synthesize their findings into one verdict. Never auto-apply changes.
Repo facts: the rules in the repo's `AGENTS.md` (or `CLAUDE.md`) and the skills it routes changes to.
## 1. Scope
Identify what to review:
- If the user names files or a diff, use that.
- On a feature branch, run `git diff <base>...HEAD` with the repo's default branch as base. Find it with git:
```sh
git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null \
|| for b in origin/main origin/master main master; do
git rev-parse --verify -q "$b" >/dev/null && { echo "$b"; break; }
done
```
If it prints nothing, ask the user for the base branch.
- If the user refers to recent work, gather those files with `git status` and `git diff`.
Collect the diff plus any context files reviewers need to understand it.
## 2. Intent
State the intent in one paragraph, drawn from the user's message, commit messages, the PR description, and the code. If the intent is unclear, ask the user in chat before spawning reviewers.
## 3. Spawn reviewersDetails
- Skill name
comms-interrogate- Repository
- jpoehnelt/skills
- Path
comms-interrogate/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
FAQ
What does the Comms Interrogate skill do?
Multi-reviewer critique of a diff, run as parallel read-only subagents from distinct angles, then synthesized into one verdict. Use for "interrogate", "adversarial review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".
How do I install the Comms Interrogate skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill comms-interrogate. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Comms Interrogate popular?
It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.
Related skills
Agents Correct
23jpoehnelt/skills
Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.
Agents Create Verification Skill
23jpoehnelt/skills
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.
Agents Reflect
23jpoehnelt/skills
After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.
Eng TDD
23jpoehnelt/skills
Fix a bug test-first when there is a clear, cheap regression test path. Use when the user asks for TDD, a failing test, or a regression test, or when the bug has an obvious cheap local test target.
Systemic Engineering
9mvellas/systemic-engineering-skill
Structure and execute software or general-system projects from stakeholder values through VFT, SSM, STPA, traceable requirements, project artifacts, and evidence-gated multi-agent delivery. Use for ambiguous or consequential projects that need rigorous discovery, safety analysis, requirements, PRDs/specs/tests, or supervised implementation; do not use for a trivial one-file change.
Eng Testing
23jpoehnelt/skills
Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.