summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorAiden Cline <[email protected]>2026-01-18 13:22:39 -0600
committerAiden Cline <[email protected]>2026-01-18 13:22:58 -0600
commitc29d44fcef12b393f82407d6fbd26b0ce8aa979a (patch)
treecf2f38ba8646aadebb36d5d0706336f6154b9964
parent38c641a2fc6d45c504d419609359f64710a4e732 (diff)
downloadopencode-c29d44fcef12b393f82407d6fbd26b0ce8aa979a.tar.gz
opencode-c29d44fcef12b393f82407d6fbd26b0ce8aa979a.zip
docs: note untracked files in review
-rw-r--r--packages/opencode/src/command/template/review.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/packages/opencode/src/command/template/review.txt b/packages/opencode/src/command/template/review.txt
index 1ffa0fca0..9f6fbfcc3 100644
--- a/packages/opencode/src/command/template/review.txt
+++ b/packages/opencode/src/command/template/review.txt
@@ -13,6 +13,7 @@ Based on the input provided, determine which type of review to perform:
1. **No arguments (default)**: Review all uncommitted changes
- Run: `git diff` for unstaged changes
- Run: `git diff --cached` for staged changes
+ - Run: `git status --short` to identify untracked (net new) files
2. **Commit hash** (40-char SHA or short hash): Review that specific commit
- Run: `git show $ARGUMENTS`
@@ -33,6 +34,7 @@ Use best judgement when processing input.
**Diffs alone are not enough.** After getting the diff, read the entire file(s) being modified to understand the full context. Code that looks wrong in isolation may be correct given surrounding logic—and vice versa.
- Use the diff to identify which files changed
+- Use `git status --short` to identify untracked files, then read their full contents
- Read the full file to understand existing patterns, control flow, and error handling
- Check for existing style guide or conventions files (CONVENTIONS.md, AGENTS.md, .editorconfig, etc.)