RU: Audit Now

Force the loop to enter validation mode on the next iteration.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

Usage

• /ru:audit-now - Start validation from round 1
• /ru:audit-now 4 - Start from round 4 (Adversarial Probing)

Execution

/usr/bin/env bash << 'RU_AUDIT_SCRIPT'
PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$(pwd)}"
CONFIG_FILE="$PROJECT_DIR/.claude/ru-config.json"
STATE_FILE="$PROJECT_DIR/.claude/ru-state.json"
ROUND="${ARGUMENTS:-1}"

# Validate round number
if ! [[ "$ROUND" =~ ^[1-5]$ ]]; then
    echo "Error: Round must be 1-5"
    echo ""
    echo "Validation Rounds:"
    echo "  1: Critical Issues"
    echo "  2: Verification"
    echo "  3: Documentation"
    echo "  4: Adversarial Probing"
    echo "  5: Cross-Period Robustness"
    exit 1
fi

# Ensure config file exists
if [[ ! -f "$CONFIG_FILE" ]]; then
    echo '{}' > "$CONFIG_FILE"
fi

# Check if loop is running
CURRENT_STATE="stopped"
if [[ -f "$STATE_FILE" ]]; then
    CURRENT_STATE=$(jq -r '.state // "stopped"' "$STATE_FILE" 2>/dev/null || echo "stopped")
fi

if [[ "$CURRENT_STATE" != "running" ]]; then
    echo "Warning: Loop not running (state: $CURRENT_STATE)"
fi

# Set force validation flag
TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
jq --argjson round "$ROUND" --arg ts "$TIMESTAMP" \
    '.force_validation = {enabled: true, round: $round, timestamp: $ts}' \
    "$CONFIG_FILE" > "$CONFIG_FILE.tmp" && mv "$CONFIG_FILE.tmp" "$CONFIG_FILE"

echo "Force validation enabled - starting round $ROUND on next iteration"
RU_AUDIT_SCRIPT

Run the bash script above to force validation mode.

Troubleshooting

Post-Execution Reflection

After this skill completes, check before closing:

1. Did the command succeed? — If not, fix the instruction or error table that caused the failure.
2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
3. Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.