xonecas.io
64875
Mc

mini-coder / commit 7a25163

Update search model, review prompt, and add streaming subagent TODO

- Update search command model to claude-haiku-4-5
- Simplify review prompt to be more concise and direct
- Add TODO for streaming subagent activity to main output

Sean2026-02-25 7a251634edc6b66b66bc1628dc5495320ff1485f parent d27dccb

3 files changed

.agents/commands/search.md+1−1
@@ -1,6 +1,6 @@
11 ---
22 description: Search the codebase for a topic using a subagent
3-model: zen/claude-3-5-haiku
3+model: zen/claude-haiku-4-5
44 ---
55
66 Search the codebase for: $ARGUMENTS
TODO.md+4−0
@@ -1,5 +1,9 @@
11 # TODO
22
3+## Streaming subagent activity
4+
5+I'd like to have the subgent output/activity to be streamed to the main output. Right now we wait for the subagent to be complete to print all at once
6+
37 ## Glob and grep ignore dot files and folders
48
59 This is just dumb and an error when implementing the spec. We are making a dev tool, it's
src/cli/commands.ts+11−25
@@ -271,31 +271,17 @@ const REVIEW_PROMPT = (cwd: string, focus: string) => `\
271271 You are a code reviewer. Review recent changes and provide actionable feedback.
272272
273273 Working directory: ${cwd}
274-${focus ? `Focus: ${focus}` : ""}
275-
276-## What to review
277-- No args: \`git diff\` (unstaged) + \`git diff --cached\` (staged) + \`git status --short\` (untracked)
278-- Commit hash: \`git show <hash>\`
279-- Branch: \`git diff <branch>...HEAD\`
280-- PR number/URL: \`gh pr view\` + \`gh pr diff\`
281-
282-## How to review
283-After getting the diff, read the full files changed — diffs alone miss context.
284-Check for AGENTS.md or CONVENTIONS.md for project conventions.
285-
286-## What to flag (priority order)
287-1. **Bugs** — logic errors, missing edge cases, unhandled errors, race conditions, security issues. Be certain before flagging; investigate first.
288-2. **Structure** — wrong abstraction, established patterns ignored, excessive nesting.
289-3. **Performance** — only if obviously problematic (O(n²) on unbounded data, N+1, blocking hot paths).
290-4. **Style** — only clear violations of project conventions. Don't be a zealot.
291-
292-Only review the changed code, not pre-existing code.
293-
294-## Output
295-- Be direct and specific: quote code, cite file and line number.
296-- State the scenario/input that triggers a bug — severity depends on this.
297-- No flattery, no filler. Matter-of-fact tone.
298-- End with a short **Summary** of the most important items.
274+${focus ? `Review: ${focus}` : "Review the current changes"}
275+
276+Perform a sensible code review:
277+
278+- Correctness: Are the changes in alignment with the goal?
279+- Code quality: Is there duplicate, dead or bad code patterns introduced or as a result of the changes?
280+- Is the code performant?
281+- Never flag style choices as bugs, don't be a zeolot.
282+- Never flag false positives, if you think something is wrong, check before saying it's an issue.
283+
284+Output a small summary with only the issues found. If nothing of note was found reply saying that.
299285 `;
300286
301287 async function handleReview(