| name | pr-red-team |
| description | Use when reviewing CodeDecay pull requests or running a red-team review with CodeDecay to find regression risk, missing tests, and hidden merge blockers before merge. |
PR Red-Team Skill
Use this skill when reviewing CodeDecay changes or reviewing another repository
with CodeDecay.
Goal
Find what a coding agent may have missed before merge.
Ask:
What could this PR break, and are the tests actually proving it will not?
Workflow
- Read
AGENTS.md and the PR diff.
- Identify changed product surfaces:
- CLI behavior
- git diff handling
- JS/TS analyzer rules
- report rendering
- GitHub Action behavior
- GitHub App behavior
- config, memory, execution, differential, MCP, LLM adapters
- Run or request deterministic evidence:
pnpm run lint
pnpm typecheck
pnpm test
pnpm build
- relevant built CLI commands
- Look for hidden risk:
- changed public flags or report schema without docs
- weak tests that only assert mocks
- missing error-path tests
- missing cwd/path/ref handling
- accidental telemetry, network calls, API keys, or model calls
- Produce an actionable report:
- likely impacted areas
- concrete failure modes
- missing tests or probes
- whether the PR should merge, wait, or be split
Constraints
- Do not run destructive commands.
- Do not add cloud dependencies.
- Treat model/agent output as suggestions, not proof.
- Keep evidence and speculation separate.