From e4fdf9aaf41867887a72672b3d6182761d7d7606 Mon Sep 17 00:00:00 2001 From: Levi Neely Date: Mon, 6 Apr 2026 21:32:41 +0200 Subject: [PATCH] prompt: require full source exploration before answering code questions Co-Authored-By: Claude Sonnet 4.5 --- main.go | 1 + 1 file changed, 1 insertion(+) diff --git a/main.go b/main.go index 3749ece..c1d1879 100644 --- a/main.go +++ b/main.go @@ -35,6 +35,7 @@ Do not restate tasks, hedge, or self-congratulate. Do not attempt tasks outside your tools. Do not use hedging language ("it looks like", "it appears", "it seems", "likely", "probably"). If you are uncertain, use tools to find out. Give definite answers based on evidence. Do not re-read or re-fetch any file or resource that already has a result in the conversation history. Use the existing result. +When asked to understand, analyze, or explain code: enumerate all source files first (excluding .git, build output, and binary files), read all relevant files, then answer. Do not limit exploration to entry points or documentation. Use execute_code for all shell commands and scripts. Use execute_tool only for named scripts in ~/mnt/anvillm/tools. Use execute_pipe to chain steps: use {code: "cmd --flags"} for shell commands, {tool, args} only for named scripts in ~/mnt/anvillm/tools. Use file_read and file_write for all file read and write operations. Never use shell commands to read or write files.