@dahawa/hawa-code 1.3.10 → 1.4.0

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.
Files changed (2) hide show
  1. package/cli.js +6 -6
  2. package/package.json +1 -1
package/cli.js CHANGED
@@ -440,12 +440,12 @@ Usage notes:
440
440
  - You can use the \`run_in_background\` parameter to run the command in the background, which allows you to continue working while the command runs. You can monitor the output using the Bash tool as it becomes available. Never use \`run_in_background\` to run 'sleep' as it will return immediately. You do not need to use '&' at the end of the command when using this parameter.
441
441
 
442
442
  - Avoid using Bash with the \`find\`, \`grep\`, \`cat\`, \`head\`, \`tail\`, \`sed\`, \`awk\`, or \`echo\` commands, unless explicitly instructed or when these commands are truly necessary for the task. Instead, always prefer using the dedicated tools for these commands:
443
- - File search: Use Glob (NOT find or ls)
444
- - Content search: Use Grep (NOT grep or rg)
445
- - Read files: Use Read (NOT cat/head/tail)
446
- - Edit files: Use Edit (NOT sed/awk)
447
- - Write files: Use Write (NOT echo >/cat <<EOF)
448
- - Communication: Output text directly (NOT echo/printf)
443
+ - File search: Use \`Glob\` tool (NOT find or ls commands)
444
+ - Content search: Use \`Grep\` tool (NOT grep or rg commands)
445
+ - Read files: Use \`Read\` tool (NOT cat/head/tail commands)
446
+ - Edit files: Use \`Edit\` tool (NOT sed/awk commands)
447
+ - Write files: Use \`Write\` tool (NOT echo >/cat <<EOF commands)
448
+ - Communication: Output text directly (NOT echo/printf commands)
449
449
  - When issuing multiple commands:
450
450
  - If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message. For example, if you need to run "git status" and "git diff", send a single message with two Bash tool calls in parallel.
451
451
  - If the commands depend on each other and must run sequentially, use a single Bash call with '&&' to chain them together (e.g., \`git add . && git commit -m "message" && git push\`). For instance, if one operation must complete before another starts (like mkdir before cp, Write before Bash for git operations, or git add before git commit), run these operations sequentially instead.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dahawa/hawa-code",
3
- "version": "1.3.10",
3
+ "version": "1.4.0",
4
4
  "bin": {
5
5
  "hcode": "hawa.js"
6
6
  },