Requesting Red Team Review
This is a structured way to catch mistakes before you commit to a conclusion. You dispatch a separate subagent with just your analysis artifacts (bounded by git SHAs, not your full session history) and an explicit mandate to find what's wrong. The reviewer looks for confounds, leakage, assumption violations, and over-claiming. It's meant to be mandatory after completing analysis steps and before reporting findings, especially when results are suspiciously clean or convenient. The pattern borrows from adversarial review in research: a conclusion that survives a genuine attack is worth trusting, one that hasn't been attacked isn't. Critical issues block reporting, Important issues get fixed before writeup, and you're expected to verify rather than dismiss feedback that stings.
- GitHub stars
- 202
- last updated
- Jun 1, 2026
Install
$ npx -y skills add k-dense-ai/science-superpowers --skill requesting-red-team-review --agent claude-codeInstalls into .claude/skills of the current project.
Files
Requesting Red-Team Review
Dispatch a reviewer subagent whose explicit job is to find why your conclusion is wrong — before you believe it or report it. The reviewer gets precisely crafted context for evaluation, never your session's history. This keeps it focused on the work product and your reasoning, not on agreeing with you, and preserves your own context.
Core principle: Try hardest to break a finding when it's most likely to be right. A result that survives a genuine attack is worth reporting; one that hasn't been attacked isn't.
When to Request Review
Mandatory:
- After each analysis step in subagent-driven-analysis (the rigor reviewer plays this role per step)
- After completing the full analysis, before writing it up
- Before claiming any confirmatory finding
Especially valuable:
- When the result is surprising, important, or convenient
- When performance is suspiciously good (possible leakage)
- After resolving an anomaly
How to Request
1. Get the git SHAs that bound the work:
BASE_SHA=$(git rev-parse HEAD~N) # before the analysis
HEAD_SHA=$(git rev-parse HEAD)
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageDetails
- Repository
- github.com/k-dense-ai/science-superpowers
- Categories
- Git & Pull Requests, Code Review & Quality
- First seen
- Jun 11, 2026
More from k-dense-ai/science-superpowers
All 15- Setting Up Reproducible Analysis
- Subagent Driven Analysis
- Surveying Prior Work
- Using Science Superpowers
- Verifying Results Before Claiming
- Writing Science Skills
- Designing The Analysis
- Dispatching Parallel Investigations
- Executing Analysis
- Framing Research Questions
- Investigating Anomalous Results
- Preregistering Analysis
- Receiving Critical Review
- Reporting And Archiving Findings
Recommended
More Git & Pull Requests
typescript-reviewmetabase/metabaseReview TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull 0skills.sh installs
commitRecidiviz/pulse-dataCommit uncommitted changes with clear commit messages. Use when the user0skills.sh installs
git-advanced-workflowsrjmurillo/ai-agentsMaster advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use wh0skills.sh installs
caveman-commitjuliusbrussee/cavemanUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars431.6Kskills.sh installs