pi-tool-discipline 0.1.3 → 0.1.4
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/extensions/index.ts +3 -2
- package/package.json +1 -1
package/extensions/index.ts
CHANGED
|
@@ -51,8 +51,9 @@ Tool priority for search (always use the highest available):
|
|
|
51
51
|
|
|
52
52
|
Rules:
|
|
53
53
|
|
|
54
|
-
-
|
|
55
|
-
-
|
|
54
|
+
- Search and read files ONLY with dedicated tools, never with bash commands.
|
|
55
|
+
- ffgrep/fffind work with absolute paths outside the workspace (separate index), and ffgrep supports regex, path and exclude filters. If a search seems to miss something, adjust its parameters (path, exclude, regex, caseSensitive) — do NOT fall back to bash \`grep\`/\`rg\`/\`find\`/\`ls\`.
|
|
56
|
+
- Read files with \`read\` (use \`offset\`/\`limit\` for large files); never use bash \`cat\`/\`head\`/\`tail\`/\`sed\` to read.
|
|
56
57
|
- Do NOT use the bash tool for \`grep\`/\`rg\`/\`find\`/\`ls\`/\`cat\`/\`sed\`/\`head\`/\`tail\`/\`which\` searches or file reads.
|
|
57
58
|
- Bash stays allowed only when dedicated tools cannot do the job: pipelines, git, npm, running programs, network requests, file mutations.
|
|
58
59
|
- If bash searching is truly unavoidable, prefer \`rg\` over \`grep\`.`;
|
package/package.json
CHANGED