fix: strengthen codebase_search enforcement throughout conversations

[hannesrudolph]

Problem

The codebase_search tool was only being enforced at the start of new tasks, not throughout entire conversations. This led to situations where the AI would use less effective search methods (like search_files or list_files) when exploring code later in a conversation, missing important context and relationships.

Solution

Updated the prompt language across multiple sections to make codebase_search enforcement continuous throughout conversations:

Changes Made

1. Tool Use Guidelines (src/core/prompts/sections/tool-use-guidelines.ts):

   • Changed from: "When starting a new task or when you need to understand existing code/functionality"
   • Changed to: "For ANY exploration of code you haven't examined yet in this conversation"
   • Added explicit statement: "This requirement applies throughout the entire conversation"

2. Rules Section (src/core/prompts/sections/rules.ts):

   • Changed from: "When you need to understand existing code or functionality"
   • Changed to: "For ANY exploration of code you haven't examined yet in this conversation"
   • Added: "regardless of when in the conversation it occurs"

3. Objective Section (src/core/prompts/sections/objective.ts):

   • Changed from: "if the task involves understanding existing code or functionality"
   • Changed to: "For ANY exploration of code you haven't examined yet in this conversation"
   • Added: "This applies throughout the entire conversation"

4. Test Updates:

   • Updated test expectations in objective.spec.ts and tool-use-guidelines.spec.ts to match the new enforcement language
   • All tests are passing

Impact

This change ensures that codebase_search is used consistently throughout conversations, improving:

• Code discovery and understanding
• Context awareness when exploring unfamiliar parts of the codebase
• Overall quality of code analysis and modifications

Testing

• ✅ All unit tests updated and passing
• ✅ Linting checks passed
• ✅ Type checking passed

---

Important

Enforces continuous use of codebase_search throughout conversations for consistent code exploration, with updates to prompt language and tests.

• Prompt Language Updates:
  • Updated tool-use-guidelines.ts, rules.ts, and objective.ts to enforce codebase_search for any new code exploration during conversations.
  • Added language to emphasize continuous enforcement, not just at task start.
• Test Updates:
  • Modified objective.spec.ts and tool-use-guidelines.spec.ts to align with new codebase_search enforcement language.
  • Ensured tests check for continuous enforcement language.
• Impact:
  • Ensures consistent use of codebase_search, improving code understanding and context awareness.
  • Enhances quality of code analysis and modifications.

^{This description was created by for 73782d9. You can customize this summary. It will automatically update as commits are pushed.}

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to 73782d9.

Security Overview

• 🔎 Scanned files: 5 changed file(s)

Detected Code Changes

Change Type	Relevant files
Enhancement	► objective.ts     Strengthen codebase_search enforcement language ► rules.ts     Update codebase_search rules with stronger enforcement ► tool-use-guidelines.ts     Enhance codebase_search tool usage guidelines
Configuration changes	► package.json     Update package version
Refactor	► objective.spec.ts     Update test expectations for new enforcement language ► tool-use-guidelines.spec.ts     Update test cases for revised tool guidelines

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

[Copilot]

Pull Request Overview

This PR strengthens the enforcement of the codebase_search tool by making it mandatory for any new code exploration throughout conversations.

• Unified prompt language to insist on codebase_search first whenever exploring unfamiliar code areas
• Updated all related sections (tool-use-guidelines, rules, objective) with continuous-enforcement wording
• Adjusted corresponding unit tests to validate the new phrasing

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/core/prompts/sections/tool-use-guidelines.ts	Made codebase_search enforcement apply throughout conversations
src/core/prompts/sections/rules.ts	Broadened rule to require semantic search for any new code area
src/core/prompts/sections/objective.ts	Changed objective text to mandate continuous codebase_search use
src/core/prompts/sections/tests/tool-use-guidelines.spec.ts	Updated test strings to match the new guideline wording
src/core/prompts/sections/tests/objective.spec.ts	Modified objective tests to check for the added enforcement note

Comments suppressed due to low confidence (1)

src/core/prompts/sections/objective.ts:14

• The objective section refers to 'entire task' while other sections mention 'entire conversation'. Consider standardizing this phrasing for consistency across all prompts.

		? "First, for ANY exploration of code you haven't examined yet in this conversation, you MUST use the `codebase_search` tool to search for relevant code based on the task's intent BEFORE using any other search or file exploration tools. This applies throughout the entire task, not just at the beginning - whenever you need to explore a new area of code, codebase_search must come first. Then, "

[daniel-lxs]

LGTM