deep-divelisted

# Deep Dive: $ARGUMENTS Think hard about this. Investigate deeply. Do not miss things. A deep dive is more than file auditing. It means thorough investigation of a topic, question, or concern. The scope could be a security analysis, an architecture question, a decision review, a code quality audit, or anything that needs careful thought. ## Phase 0: Commit-anchored delta (for file/repo audits) Skip Phase 0 if the scope is a pure concept (architecture question, decision review). For audits of files, directories, or repos: 1. **Establish the last anchor.** Check when you last reviewed this scope - use a git SHA, a timestamp file, or a prior audit record. If no prior anchor: full dive, read everything. 2. **Get only what changed:** ```bash git log --name-only --pretty=format: <anchor>..HEAD -- <path> | sort -u | grep -v '^$' ``` Review ONLY the files that changed. Re-reading unchanged files is exactly the waste this prevents. 3. **Also check deletions** (for impact analysis): ```bash git log --name-only --pretty=format: --diff-filter=D <anchor>..HEAD -- <path> | sort -u | grep -v '^$' ``` 4. **Record a new anchor** after the dive (git SHA or timestamp) so the next run can delta from here. ## Investigation (Phase 1+) 1. **Understand what is being asked.** Arguments may be a question, concern, file, repo, or topic. Adapt. 2. **Think from first principles.** Do not just check checklists. What could go wrong? What assumptions are baked in? For complex