repowisestage 0.0.60 → 0.0.61
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/bin/repowise.js +2 -2
- package/package.json +1 -1
package/dist/bin/repowise.js
CHANGED
|
@@ -3046,7 +3046,7 @@ Treat RepoWise as your default starting point for every task that touches this c
|
|
|
3046
3046
|
2. **Use the three-tier hierarchy in this order:**
|
|
3047
3047
|
- **Tier 1 \u2014 RepoWise MCP** for surgical structural queries: symbol resolution, callers, references, call graphs, refactor impact, dependency graphs, type info (\`find_symbol\`, \`get_impact\`, \`lsp_definition\`, etc. \u2014 the server is named "RepoWise MCP for <repo>", so hosts that prefix tool names expose them accordingly). Each tool's description tells you when to use it.
|
|
3048
3048
|
- **Tier 2 \u2014 Context files in \`repowise-context/\`** for narrative context: how a domain is designed, what patterns exist, what conventions to follow. Use the *Context File Routing Map* below to pick which files to read.
|
|
3049
|
-
- **Tier 3 \u2014 Native code search** (\`read_file\` / \`grep\` / \`glob\` on raw source) ONLY when tiers 1-2 don't cover the question, or for ephemeral state (recent commits, in-flight branches).
|
|
3049
|
+
- **Tier 3 \u2014 Native code search** (\`read_file\` / \`grep\` / \`glob\` on raw source) ONLY when tiers 1-2 don't cover the question, or for ephemeral state (recent commits, in-flight branches). An enforcement hook may DENY a Tier-3 search until you have used Tier 1 or Tier 2 this turn \u2014 that is expected, not an error: consult RepoWise first, then retry the same search and it will proceed.
|
|
3050
3050
|
|
|
3051
3051
|
3. **Batch tool calls in parallel.** For maximum efficiency, whenever you need multiple independent operations to gather context, invoke all relevant tools SIMULTANEOUSLY rather than sequentially. Examples:
|
|
3052
3052
|
- Reading 3 context files \u2192 3 \`read_file\` calls in parallel.
|
|
@@ -3072,7 +3072,7 @@ Treat RepoWise as your default starting point for every task that touches this c
|
|
|
3072
3072
|
|
|
3073
3073
|
That's it \u2014 one short line, no longer preamble. The host's tool-call UI already shows RepoWise MCP calls visibly; this tag adds the same surface for context-file reads. If you didn't use RepoWise on this turn, omit the tag \u2014 never fake it.
|
|
3074
3074
|
|
|
3075
|
-
8. **
|
|
3075
|
+
8. **MCP unavailable vs. a RepoWise miss \u2014 handle them differently.** If RepoWise MCP is entirely unavailable (no \`.mcp.json\` configured, listener not running), tell the user. But if RepoWise IS available and simply does not cover a specific question, just continue with Tier 3 \u2014 do NOT announce that "RepoWise doesn't have it." That fallback is normal and expected; the system records it on its own to improve coverage.
|
|
3076
3076
|
${END_MARKER}`;
|
|
3077
3077
|
function injectAgentInstructions(content) {
|
|
3078
3078
|
const lineEnding = content.includes("\r\n") ? "\r\n" : "\n";
|