pr-redteam-staged

/redteam-pr:staged Command

Adversarial red team analysis of staged git changes for PR review.

Usage

/redteam-pr:staged [mode]

Arguments

mode (optional):

• quick - Fast 2-3 vector analysis, skip grounding
• standard - Balanced 5-6 vectors with basic grounding (default)
• deep - All categories + meta-analysis with full grounding
• focus:[category] - Deep dive on specific category (e.g., focus:reasoning-flaws)

Instructions

You are the MINIMAL entry point for PR red team analysis of staged changes. Your ONLY job is to:

1. Execute git operations to get staged changes
2. Check PAL MCP availability (optional enhancement)
3. Extract diff metadata and build structured snapshot
4. Launch the pr-analysis-coordinator agent with the snapshot
5. Return the coordinator's output directly to the user

Step 1: Execute Git Operations

Use the Bash tool to get staged changes:

# Get file statistics
git diff --cached --numstat

# Get unified diff with 3 lines of context
git diff --cached -U3

If no staged changes exist, inform the user and exit.

Step 2: Check PAL Availability (Non-Blocking)

Launch the pal-availability-checker agent to detect if PAL MCP is available:

Task: Launch pal-availability-checker agent
Agent: agents/pal-availability-checker.md
Prompt: Check if PAL MCP is available and list models

Parse the YAML result and include pal_available: true/false in the snapshot. This step is NON-BLOCKING - continue regardless of result. PAL is optional.

Step 3: Parse Mode

Determine mode from command arguments:

• Default mode: standard

Step 4: Extract Diff Metadata

Parse the git output to build structured metadata:

From git diff --cached --numstat:

• Extract file paths, additions, deletions
• Classify change_type: added, modified, deleted, renamed

Calculate risk_score per file:

• Base score: 0.0
• Authentication/security files (auth, security, permission in path): +0.4
• Large changes (>100 lines added/deleted): +0.3
• Test files (test, spec in path): -0.3
• Clamp to [0.0, 1.0]