qalisted

# QA — Codex-Powered Change Review Thorough QA on all changes in the current working tree using Codex as a second pair of eyes. Detects what changed, sends it to Codex for deep review, and presents actionable findings. ## When to Use - After completing implementation work, before committing - User says "QA", "full QA", "QA my changes", "review with codex" - Any time you want a second opinion on everything you just built ## Process ### Step 1: Gather All Changes ```bash # Get the full picture git status --porcelain git diff --stat git diff --cached --stat # Capture the actual diff (staged + unstaged) git diff HEAD > /tmp/qa-full-diff.patch ``` If changes span many files, also get a summary: ```bash git diff HEAD --name-only ``` ### Step 2: Build Context Before sending to Codex, gather context about what was being built: - What task/feature was being implemented? - What files were touched and why? - Any known areas of concern? Summarize this in 2-3 sentences to give Codex context. ### Step 3: Codex Review (diff-based) Run Codex with the full diff and context. Use `-C` to point at the repo so Codex can read surrounding code. ```bash cat <<'PROMPT' | codex exec --full-auto -C "$(git rev-parse --show-toplevel)" -o /tmp/qa-codex-review.md - You are doing a thorough QA review of the following changes. Be critical — find real bugs, not style nits. ## Context [2-3 sentence summary of what was built] ## Your Review Checklist 1. **Correctness**: Logic errors, off-by-ones