ai-qakit 1.0.0

package/templates/.claude/skills/claude-code-analyzer/scripts/analyze.sh

@@ -0,0 +1,274 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+# Claude Code History Analyzer - Fixed Version
+# Key fixes:
+# 1. Simplified jq syntax (remove != null checks)
+# 2. Better error handling for empty results
+# 3. Validate temp files before JSON generation
+# 4. More robust file processing
+
+# Parse arguments
+CURRENT_PROJECT_ONLY=false
+SINGLE_FILE=""
+SETTINGS_FILE="${HOME}/.claude/settings.json"
+DISCOVER_GITHUB=true
+
+while [[ $# -gt 0 ]]; do
+  case $1 in
+  --current-project)
+    CURRENT_PROJECT_ONLY=true
+    shift
+    ;;
+  --file)
+    SINGLE_FILE="$2"
+    shift 2
+    ;;
+  --discover-github)
+    DISCOVER_GITHUB=true
+    shift
+    ;;
+  *)
+    shift
+    ;;
+  esac
+done
+
+CLAUDE_PROJECTS_DIR="${HOME}/.claude/projects"
+
+# Colors for status output (to stderr)
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+NC='\033[0m'
+
+# Check if jq is installed
+if ! command -v jq &>/dev/null; then
+  echo -e "${RED}Error: jq is required but not installed${NC}" >&2
+  echo "Install with: brew install jq (macOS) or apt install jq (Linux)" >&2
+  exit 1
+fi
+
+# Create temporary files for aggregation
+TEMP_DIR=$(mktemp -d)
+TOOLS_FILE="$TEMP_DIR/tools.txt"
+PROJECTS_FILE="$TEMP_DIR/projects.txt"
+MODELS_FILE="$TEMP_DIR/models.txt"
+AUTO_ALLOWED_FILE="$TEMP_DIR/auto_allowed.txt"
+
+# Cleanup on exit
+trap "rm -rf '$TEMP_DIR'" EXIT
+
+# Read existing auto-allowed tools from settings
+if [ -f "$SETTINGS_FILE" ]; then
+  jq -r '.autoAllowedTools[]? // empty' "$SETTINGS_FILE" 2>/dev/null | sort >"$AUTO_ALLOWED_FILE" || touch "$AUTO_ALLOWED_FILE"
+else
+  touch "$AUTO_ALLOWED_FILE"
+fi
+
+echo -e "${BLUE}Claude Code History Analyzer${NC}" >&2
+echo -e "${BLUE}=============================${NC}\n" >&2
+
+# Determine which files to analyze
+if [ -n "$SINGLE_FILE" ]; then
+  if [ ! -f "$SINGLE_FILE" ]; then
+    echo -e "${RED}Error: File not found: $SINGLE_FILE${NC}" >&2
+    exit 1
+  fi
+  echo -e "Analyzing single file: ${GREEN}$(basename "$SINGLE_FILE")${NC}\n" >&2
+  FILES_TO_ANALYZE=("$SINGLE_FILE")
+  SCOPE="single_file"
+  SCOPE_DETAIL="$(basename "$SINGLE_FILE")"
+
+elif [ "$CURRENT_PROJECT_ONLY" = true ]; then
+  CURRENT_DIR=$(pwd)
+  PROJECT_PATH=$(echo "$CURRENT_DIR" | sed 's/\//-/g')
+  PROJECT_DIR="${CLAUDE_PROJECTS_DIR}/${PROJECT_PATH}"
+
+  if [ ! -d "$PROJECT_DIR" ]; then
+    echo -e "${RED}Error: No Claude Code history found for current project${NC}" >&2
+    echo -e "Looking for: $PROJECT_DIR" >&2
+    exit 1
+  fi
+
+  echo -e "Analyzing current project: ${GREEN}${CURRENT_DIR}${NC}\n" >&2
+  mapfile -t FILES_TO_ANALYZE < <(find "$PROJECT_DIR" -name "*.jsonl" 2>/dev/null)
+  SCOPE="current_project"
+  SCOPE_DETAIL="$CURRENT_DIR"
+
+else
+  if [ ! -d "$CLAUDE_PROJECTS_DIR" ]; then
+    echo -e "${RED}Error: Claude Code projects directory not found at $CLAUDE_PROJECTS_DIR${NC}" >&2
+    exit 1
+  fi
+
+  mapfile -t FILES_TO_ANALYZE < <(find "$CLAUDE_PROJECTS_DIR" -name "*.jsonl" 2>/dev/null)
+  SCOPE="all_projects"
+  SCOPE_DETAIL=""
+fi
+
+TOTAL_FILES=${#FILES_TO_ANALYZE[@]}
+echo -e "Found ${GREEN}${TOTAL_FILES}${NC} conversation file(s)\n" >&2
+
+if [ "$TOTAL_FILES" -eq 0 ]; then
+  echo -e "${RED}No conversation files found${NC}" >&2
+  exit 1
+fi
+
+# Extract all tool usage - FIXED: Simplified jq syntax
+echo -e "${YELLOW}Extracting tool usage...${NC}" >&2
+for file in "${FILES_TO_ANALYZE[@]}"; do
+  # Process one file at a time to avoid memory issues
+  jq -r 'select(.message.content) | .message.content[] | select(.type == "tool_use") | .name' "$file" 2>/dev/null || true
+done | sort | uniq -c | sort -rn >"$TOOLS_FILE"
+
+# Check if we got any results
+if [ ! -s "$TOOLS_FILE" ]; then
+  echo -e "${YELLOW}Warning: No tool usage found in conversation files${NC}" >&2
+  touch "$TOOLS_FILE" # Create empty file to continue
+fi
+
+# Extract project paths (only if analyzing all projects)
+if [ "$CURRENT_PROJECT_ONLY" = false ] && [ -z "$SINGLE_FILE" ]; then
+  echo -e "${YELLOW}Extracting project distribution...${NC}" >&2
+  find "$CLAUDE_PROJECTS_DIR" -type d -mindepth 1 -maxdepth 1 2>/dev/null |
+    while read -r dir; do
+      count=$(find "$dir" -name "*.jsonl" 2>/dev/null | wc -l | tr -d ' ')
+      basename=$(basename "$dir")
+      echo "$count $basename"
+    done | sort -rn >"$PROJECTS_FILE"
+fi
+
+# Extract model usage - FIXED: Simplified jq syntax
+echo -e "${YELLOW}Extracting model usage...${NC}" >&2
+for file in "${FILES_TO_ANALYZE[@]}"; do
+  jq -r 'select(.message.model) | .message.model' "$file" 2>/dev/null || true
+done | sort | uniq -c | sort -rn >"$MODELS_FILE"
+
+# Check if we got any results
+if [ ! -s "$MODELS_FILE" ]; then
+  echo -e "${YELLOW}Warning: No model usage found in conversation files${NC}" >&2
+  touch "$MODELS_FILE"
+fi
+
+echo -e "${GREEN}✓ Data extraction complete!${NC}\n" >&2
+echo -e "${BLUE}Outputting structured data for analysis...${NC}\n" >&2
+
+# Output structured data as JSON for Claude to interpret
+cat <<EOF
+{
+  "metadata": {
+    "generated_at": "$(date -u +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null || date +"%Y-%m-%dT%H:%M:%SZ")",
+    "scope": "$SCOPE",
+    "scope_detail": "$SCOPE_DETAIL",
+    "total_conversations": $TOTAL_FILES
+  },
+  "tool_usage": [
+EOF
+
+# Tool usage array - FIXED: Handle empty file
+if [ -s "$TOOLS_FILE" ]; then
+  first=true
+  while read -r count tool; do
+    if [ "$first" = true ]; then
+      first=false
+    else
+      echo ","
+    fi
+    # Escape tool name for JSON
+    tool_escaped=$(echo "$tool" | sed 's/"/\\"/g')
+    printf '    {"tool": "%s", "count": %d}' "$tool_escaped" "$count"
+  done <"$TOOLS_FILE"
+  echo ""
+fi
+
+cat <<EOF
+  ],
+  "auto_allowed_tools": [
+EOF
+
+# Auto-allowed tools array - FIXED: Handle empty file
+if [ -s "$AUTO_ALLOWED_FILE" ]; then
+  first=true
+  while read -r tool; do
+    if [ "$first" = true ]; then
+      first=false
+    else
+      echo ","
+    fi
+    tool_escaped=$(echo "$tool" | sed 's/"/\\"/g')
+    usage=$(grep -w "$tool" "$TOOLS_FILE" 2>/dev/null | awk '{print $1}' || echo "0")
+    printf '    {"tool": "%s", "usage_count": %d}' "$tool_escaped" "$usage"
+  done <"$AUTO_ALLOWED_FILE"
+  echo ""
+fi
+
+cat <<EOF
+  ],
+  "model_usage": [
+EOF
+
+# Model usage array - FIXED: Handle empty file
+if [ -s "$MODELS_FILE" ]; then
+  first=true
+  while read -r count model; do
+    if [ "$first" = true ]; then
+      first=false
+    else
+      echo ","
+    fi
+    model_escaped=$(echo "$model" | sed 's/"/\\"/g')
+    printf '    {"model": "%s", "count": %d}' "$model_escaped" "$count"
+  done <"$MODELS_FILE"
+  echo ""
+fi
+
+echo "  ]"
+
+# Add project activity if available
+if [ "$CURRENT_PROJECT_ONLY" = false ] && [ -z "$SINGLE_FILE" ] && [ -s "$PROJECTS_FILE" ]; then
+  cat <<EOF
+,
+  "project_activity": [
+EOF
+
+  first=true
+  while read -r count project; do
+    if [ "$first" = true ]; then
+      first=false
+    else
+      echo ","
+    fi
+    # Decode project path
+    project_decoded=$(echo "$project" | sed 's/-/\//g' | sed 's/^/~/')
+    project_escaped=$(echo "$project_decoded" | sed 's/"/\\"/g')
+    printf '    {"project": "%s", "conversations": %d}' "$project_escaped" "$count"
+  done <"$PROJECTS_FILE"
+
+  echo ""
+  echo "  ]"
+fi
+
+echo "}"
+
+# Add GitHub discovery data if requested
+if [ "$DISCOVER_GITHUB" = true ]; then
+  SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+  echo -e "\n${BLUE}Running GitHub discovery...${NC}" >&2
+
+  # Run GitHub discovery and capture output
+  if [ -f "$SCRIPT_DIR/github-discovery.sh" ]; then
+    # FIXED: Only add JSON continuation if GitHub discovery succeeds
+    if output=$(bash "$SCRIPT_DIR/github-discovery.sh" all 2>/dev/null); then
+      echo ","
+      echo '"github_discovery": '
+      echo "$output"
+    else
+      echo -e "${YELLOW}Warning: GitHub discovery failed or returned no results${NC}" >&2
+    fi
+  else
+    echo -e "${YELLOW}Warning: github-discovery.sh not found${NC}" >&2
+  fi
+fi

package/templates/.claude/skills/claude-code-analyzer/scripts/fetch-features.sh

@@ -0,0 +1,69 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+# Claude Code Feature Analyzer
+# Fetches latest docs and compares with user's actual usage patterns
+
+CLAUDE_DOCS_URL="https://docs.claude.com/en/docs/claude-code"
+TEMP_DIR=$(mktemp -d)
+DOCS_FILE="$TEMP_DIR/claude-code-docs.html"
+FEATURES_FILE="$TEMP_DIR/features.txt"
+
+# Colors
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+NC='\033[0m'
+
+echo -e "${BLUE}Fetching latest Claude Code documentation...${NC}\n"
+
+# Try to fetch docs
+if command -v curl &> /dev/null; then
+    if curl -s -L "$CLAUDE_DOCS_URL" -o "$DOCS_FILE" 2>/dev/null; then
+        echo -e "${GREEN}✓ Documentation fetched${NC}\n"
+    else
+        echo -e "${YELLOW}⚠ Could not fetch docs, using fallback feature list${NC}\n"
+        DOCS_FILE=""
+    fi
+else
+    echo -e "${YELLOW}⚠ curl not found, using fallback feature list${NC}\n"
+    DOCS_FILE=""
+fi
+
+# Known Claude Code features (fallback + common features)
+cat > "$FEATURES_FILE" <<'EOF'
+Agents: Custom AI assistants for specific tasks
+Slash Commands: Quick shortcuts for common operations
+Skills: Modular capabilities you can add
+Tool Auto-Allow: Automatically approve specific tools
+Project Context: Automatic codebase understanding
+Git Integration: Native git operations
+Terminal Integration: Execute commands directly
+File Watching: Automatic file change detection
+Multi-file Editing: Edit multiple files simultaneously
+Code Generation: Create new files and boilerplate
+Refactoring: Automated code improvements
+Testing: Generate and run tests
+Documentation: Auto-generate docs from code
+Search: Advanced codebase search
+Context Memory: Remember past interactions
+Web Search: Look up current information
+API Integration: Connect to external services
+Custom Tools: Build your own tools
+Workflows: Chain multiple operations
+Templates: Reusable code patterns
+EOF
+
+echo -e "${BLUE}Available Claude Code Features${NC}"
+echo -e "${BLUE}==============================${NC}\n"
+
+while IFS=: read -r feature description; do
+    echo "📌 $feature"
+    echo "   $description"
+    echo ""
+done < "$FEATURES_FILE"
+
+# Cleanup
+rm -rf "$TEMP_DIR"
+
+echo -e "${GREEN}Feature list complete${NC}"

package/templates/.claude/skills/claude-code-analyzer/scripts/github-discovery.sh

@@ -0,0 +1,178 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+# GitHub Claude Code Discovery
+# Searches GitHub for skills, agents, and slash commands based on usage patterns
+
+# Parse arguments
+SEARCH_TYPE="${1:-all}" # all, agents, skills, commands
+QUERY="${2:-}"
+
+# Colors
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+RED='\033[0;31m'
+NC='\033[0m'
+
+# Check if gh CLI is installed
+HAS_GH=false
+if command -v gh &>/dev/null; then
+  HAS_GH=true
+fi
+
+echo -e "${BLUE}GitHub Claude Code Discovery${NC}" >&2
+echo -e "${BLUE}============================${NC}\n" >&2
+
+# Function to search GitHub using gh CLI
+search_with_gh() {
+  local path="$1"
+  local query="$2"
+  local limit="${3:-10}"
+
+  if [ -z "$query" ]; then
+    gh search code "path:$path" --limit "$limit" --json path,repository,url 2>/dev/null
+  else
+    gh search code "$query path:$path" --limit "$limit" --json path,repository,url 2>/dev/null
+  fi
+}
+
+# Function to search GitHub using web URLs (fallback)
+get_search_url() {
+  local path="$1"
+  local query="$2"
+
+  if [ -z "$query" ]; then
+    echo "https://github.com/search?type=code&q=path:${path}"
+  else
+    # URL encode the query
+    query_encoded=$(echo "$query" | sed 's/ /+/g')
+    echo "https://github.com/search?type=code&q=${query_encoded}+path:${path}"
+  fi
+}
+
+# Output JSON structure
+cat <<EOF
+{
+  "has_gh_cli": $HAS_GH,
+  "searches": [
+EOF
+
+first_search=true
+
+# Search for agents
+if [ "$SEARCH_TYPE" = "all" ] || [ "$SEARCH_TYPE" = "agents" ]; then
+  if [ "$first_search" = false ]; then
+    echo ","
+  fi
+  first_search=false
+
+  echo -e "${YELLOW}Searching for agents...${NC}" >&2
+
+  cat <<EOF
+    {
+      "type": "agents",
+      "path": ".claude/agents",
+      "web_url": "$(get_search_url ".claude/agents" "$QUERY")",
+EOF
+
+  if [ "$HAS_GH" = true ]; then
+    echo '      "results": '
+    search_with_gh ".claude/agents" "$QUERY" 20 || echo '[]'
+  else
+    echo '      "results": []'
+  fi
+
+  echo -n "    }"
+fi
+
+# Search for skills
+if [ "$SEARCH_TYPE" = "all" ] || [ "$SEARCH_TYPE" = "skills" ]; then
+  if [ "$first_search" = false ]; then
+    echo ","
+  fi
+  first_search=false
+
+  echo -e "${YELLOW}Searching for skills...${NC}" >&2
+
+  cat <<EOF
+    {
+      "type": "skills",
+      "path": ".claude/skills",
+      "web_url": "$(get_search_url ".claude/skills" "$QUERY")",
+EOF
+
+  if [ "$HAS_GH" = true ]; then
+    echo '      "results": '
+    search_with_gh ".claude/skills" "$QUERY" 20 || echo '[]'
+  else
+    echo '      "results": []'
+  fi
+
+  echo -n "    }"
+fi
+
+# Search for slash commands
+if [ "$SEARCH_TYPE" = "all" ] || [ "$SEARCH_TYPE" = "commands" ]; then
+  if [ "$first_search" = false ]; then
+    echo ","
+  fi
+  first_search=false
+
+  echo -e "${YELLOW}Searching for slash commands...${NC}" >&2
+
+  cat <<EOF
+    {
+      "type": "slash_commands",
+      "path": ".claude/commands",
+      "web_url": "$(get_search_url ".claude/commands" "$QUERY")",
+EOF
+
+  if [ "$HAS_GH" = true ]; then
+    echo '      "results": '
+    search_with_gh ".claude/commands" "$QUERY" 20 || echo '[]'
+  else
+    echo '      "results": []'
+  fi
+
+  echo -n "    }"
+fi
+
+# Search for CLAUDE.md project context files
+if [ "$SEARCH_TYPE" = "all" ] || [ "$SEARCH_TYPE" = "context" ]; then
+  if [ "$first_search" = false ]; then
+    echo ","
+  fi
+  first_search=false
+
+  echo -e "${YELLOW}Searching for project context files...${NC}" >&2
+
+  cat <<EOF
+    {
+      "type": "project_context",
+      "path": ".claude/CLAUDE.md",
+      "web_url": "$(get_search_url ".claude/CLAUDE.md" "$QUERY")",
+EOF
+
+  if [ "$HAS_GH" = true ]; then
+    echo '      "results": '
+    search_with_gh ".claude/CLAUDE.md" "$QUERY" 20 || echo '[]'
+  else
+    echo '      "results": []'
+  fi
+
+  echo -n "    }"
+fi
+
+cat <<EOF
+
+  ]
+}
+EOF
+
+echo -e "\n${GREEN}✓ Search complete!${NC}" >&2
+
+if [ "$HAS_GH" = false ]; then
+  echo -e "${YELLOW}Note: Install 'gh' CLI for direct search results${NC}" >&2
+  echo -e "Install: ${BLUE}brew install gh${NC} (macOS) or see https://cli.github.com" >&2
+fi

package/templates/.claude/skills/code-review/SKILL.md

@@ -0,0 +1,155 @@
+---
+name: code-review
+description: Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, before making any completion/success claims, or when providing constructive code review to human developers. Covers receiving feedback with technical rigor, requesting reviews via code-reviewer subagent, verification gates requiring evidence before claims, and human code review best practices. Essential for subagent-driven development, pull requests, preventing false completion claims, and mentoring developers.
+---
+
+# Code Review
+
+Guide proper code review practices emphasizing technical rigor, evidence-based claims, and verification over performative responses.
+
+## Overview
+
+Code review requires three distinct practices:
+
+1. **Receiving feedback** - Technical evaluation over performative agreement
+2. **Requesting reviews** - Systematic review via code-reviewer subagent
+3. **Verification gates** - Evidence before any completion claims
+
+Each practice has specific triggers and protocols detailed in reference files.
+
+## Core Principle
+
+Always honoring **YAGNI**, **KISS**, and **DRY** principles.
+**Be honest, be brutal, straight to the point, and be concise.**
+
+**Technical correctness over social comfort.** Verify before implementing. Ask before assuming. Evidence before claims.
+
+## When to Use This Skill
+
+### Receiving Feedback
+Trigger when:
+- Receiving code review comments from any source
+- Feedback seems unclear or technically questionable
+- Multiple review items need prioritization
+- External reviewer lacks full context
+- Suggestion conflicts with existing decisions
+
+**Reference:** `references/code-review-reception.md`
+
+### Requesting Review
+Trigger when:
+- Completing tasks in subagent-driven development (after EACH task)
+- Finishing major features or refactors
+- Before merging to main branch
+- Stuck and need fresh perspective
+- After fixing complex bugs
+
+**Reference:** `references/requesting-code-review.md`
+
+### Verification Gates
+Trigger when:
+- About to claim tests pass, build succeeds, or work is complete
+- Before committing, pushing, or creating PRs
+- Moving to next task
+- Any statement suggesting success/completion
+- Expressing satisfaction with work
+
+**Reference:** `references/verification-before-completion.md`
+
+## Quick Decision Tree
+
+```
+SITUATION?
+│
+├─ Received feedback
+│  ├─ Unclear items? → STOP, ask for clarification first
+│  ├─ From human partner? → Understand, then implement
+│  └─ From external reviewer? → Verify technically before implementing
+│
+├─ Completed work
+│  ├─ Major feature/task? → Request code-reviewer subagent review
+│  └─ Before merge? → Request code-reviewer subagent review
+│
+└─ About to claim status
+   ├─ Have fresh verification? → State claim WITH evidence
+   └─ No fresh verification? → RUN verification command first
+```
+
+## Receiving Feedback Protocol
+
+### Response Pattern
+READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT
+
+### Key Rules
+- ❌ No performative agreement: "You're absolutely right!", "Great point!", "Thanks for [anything]"
+- ❌ No implementation before verification
+- ✅ Restate requirement, ask questions, push back with technical reasoning, or just start working
+- ✅ If unclear: STOP and ask for clarification on ALL unclear items first
+- ✅ YAGNI check: grep for usage before implementing suggested "proper" features
+
+### Source Handling
+- **Human partner:** Trusted - implement after understanding, no performative agreement
+- **External reviewers:** Verify technically correct, check for breakage, push back if wrong
+
+**Full protocol:** `references/code-review-reception.md`
+
+## Requesting Review Protocol
+
+### When to Request
+- After each task in subagent-driven development
+- After major feature completion
+- Before merge to main
+
+### Process
+1. Get git SHAs: `BASE_SHA=$(git rev-parse HEAD~1)` and `HEAD_SHA=$(git rev-parse HEAD)`
+2. Dispatch code-reviewer subagent via Task tool with: WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, DESCRIPTION
+3. Act on feedback: Fix Critical immediately, Important before proceeding, note Minor for later
+
+**Full protocol:** `references/requesting-code-review.md`
+
+## Verification Gates Protocol
+
+### The Iron Law
+**NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE**
+
+### Gate Function
+IDENTIFY command → RUN full command → READ output → VERIFY confirms claim → THEN claim
+
+Skip any step = lying, not verifying
+
+### Requirements
+- Tests pass: Test output shows 0 failures
+- Build succeeds: Build command exit 0
+- Bug fixed: Test original symptom passes
+- Requirements met: Line-by-line checklist verified
+
+### Red Flags - STOP
+Using "should"/"probably"/"seems to", expressing satisfaction before verification, committing without verification, trusting agent reports, ANY wording implying success without running verification
+
+**Full protocol:** `references/verification-before-completion.md`
+
+## Integration with Workflows
+
+- **Subagent-Driven:** Review after EACH task, verify before moving to next
+- **Pull Requests:** Verify tests pass, request code-reviewer review before merge
+- **General:** Apply verification gates before any status claims, push back on invalid feedback
+
+## Human Code Review Practices
+
+When reviewing code for human developers or providing constructive feedback, see comprehensive guidance in `references/human-code-review-practices.md`:
+
+- Effective feedback patterns (questions vs commands)
+- Security review checklists
+- Language-specific patterns (Python, TypeScript, etc.)
+- Test quality review guidelines
+- Handling disagreements professionally
+- PR review templates
+
+## Bottom Line
+
+1. Technical rigor over social performance - No performative agreement
+2. Systematic review processes - Use code-reviewer subagent
+3. Evidence before claims - Verification gates always
+4. Human reviews require constructive, educational feedback - See references
+
+Verify. Question. Then implement. Evidence. Then claim.