@kolisachint/hoocode-agent 0.4.6 → 0.4.7

package/examples/extensions/custom-provider-anthropic/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@kolisachint/hoocode-extension-custom-provider-anthropic",
 	"private": true,
-	"version": "0.2.6",
+	"version": "0.2.7",
 	"type": "module",
 	"engines": {
 		"bun": ">=1.0.0"

package/examples/extensions/custom-provider-gitlab-duo/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@kolisachint/hoocode-extension-custom-provider-gitlab-duo",
 	"private": true,
-	"version": "0.2.6",
+	"version": "0.2.7",
 	"type": "module",
 	"engines": {
 		"bun": ">=1.0.0"

package/examples/extensions/sandbox/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@kolisachint/hoocode-extension-sandbox",
 	"private": true,
-	"version": "0.2.6",
+	"version": "0.2.7",
 	"type": "module",
 	"engines": {
 		"bun": ">=1.0.0"

package/examples/extensions/with-deps/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@kolisachint/hoocode-extension-with-deps",
 	"private": true,
-	"version": "0.2.6",
+	"version": "0.2.7",
 	"type": "module",
 	"engines": {
 		"bun": ">=1.0.0"

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@kolisachint/hoocode-agent",
-	"version": "0.4.6",
+	"version": "0.4.7",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"type": "module",
 	"hoocodeConfig": {
@@ -44,9 +44,9 @@
 		"prepublishOnly": "npm run clean && npm run build"
 	},
 	"dependencies": {
-		"@kolisachint/hoocode-agent-core": "^0.4.6",
-		"@kolisachint/hoocode-ai": "^0.4.6",
-		"@kolisachint/hoocode-tui": "^0.4.6",
+		"@kolisachint/hoocode-agent-core": "^0.4.7",
+		"@kolisachint/hoocode-ai": "^0.4.7",
+		"@kolisachint/hoocode-tui": "^0.4.7",
 		"@silvia-odwyer/photon-node": "^0.3.4",
 		"chalk": "^5.5.0",
 		"cli-highlight": "^2.1.11",

package/templates/subagent/edit.md

@@ -10,6 +10,11 @@ Method:
 3. Make the smallest change that fully satisfies the task.
 4. Verify your edits by re-reading the changed regions.
 
+Guidance:
+- **Break down:** If the task involves multiple files or steps, list them in order before starting. Handle one logical unit at a time (one file or one cohesive change set). Do not batch unrelated edits.
+- **Summarize:** Your final answer should start with what changed and why, then list each modified file with path:line and a brief description. Mention any follow-up the caller should handle.
+- **Proceed:** If you hit a blocker (missing types, failing tests, unclear requirements), stop and report it. State what you tried, the exact error or confusion, and what you need from the caller. Do not leave the codebase in a broken state.
+
 Output:
 - Your final message must contain ONLY your answer — it is the only thing the caller receives.
 - Summarize what you changed and where (path:line), and any follow-up the caller should know.

package/templates/subagent/explore.md

@@ -9,6 +9,11 @@ Method:
 2. Search broadly, then read the specific files that matter.
 3. Trace logic across files; note exact paths and line numbers.
 
+Guidance:
+- **Break down:** Before searching, restate the task as 2–4 concrete questions you need answered. Tackle them in order of dependency (answer prerequisites first).
+- **Summarize:** Structure findings as: (1) a one-sentence summary, (2) key findings with path:line, (3) how the pieces connect. Put the most important discovery first.
+- **Proceed:** If you cannot locate something after reasonable searching, say what you looked in and what you need from the caller. Do not guess. If the codebase is large, note where you stopped and what remains unverified.
+
 Output:
 - Your final message must contain ONLY your findings — it is the only thing the caller receives.
 - Be concise and concrete: what you found, where (path:line), and how the pieces connect.

package/templates/subagent/fix.md

@@ -10,6 +10,11 @@ Method:
 3. Apply the minimal correct fix, matching existing style.
 4. Verify: re-run the relevant test or command to confirm the fix.
 
+Guidance:
+- **Break down:** Split the diagnosis into steps: (a) locate the symptom, (b) trace to root cause, (c) design fix, (d) apply and verify. Do not skip verification.
+- **Summarize:** Report in order: root cause in one sentence, files changed with path:line, what the fix does, and the verification result (pass/fail with command output summary). If verification fails, explain what happened.
+- **Proceed:** If you cannot reproduce the issue or the fix does not work after a reasonable attempt, report what you checked, what hypotheses you ruled out, and what information you need. Do not apply speculative fixes.
+
 Output:
 - Your final message must contain ONLY your answer — it is the only thing the caller receives.
 - Give the root cause, the fix (files and path:line), and the verification result.

package/templates/subagent/review.md

@@ -9,6 +9,11 @@ Method:
 2. Look for bugs, edge cases, security issues, and deviations from project conventions.
 3. Prioritize correctness over style nits.
 
+Guidance:
+- **Break down:** Review in layers: (1) correctness and logic, (2) edge cases and error handling, (3) security/safety, (4) clarity and naming. Stop when diminishing returns set in; do not nitpick trivial style.
+- **Summarize:** Start with an overall verdict (approve / approve with minor suggestions / needs changes). Then list findings ordered by severity, each with path:line and a concrete suggestion. If nothing is wrong, say so explicitly.
+- **Proceed:** If you lack context to judge a section (e.g., missing related files), note what you could not review and why. Do not fabricate issues to fill space.
+
 Output:
 - Your final message must contain ONLY your answer — it is the only thing the caller receives.
 - List findings ordered by severity, each with path:line and a concrete suggestion.

package/templates/subagent/test.md

@@ -9,6 +9,11 @@ Method:
 2. Run it. Capture pass/fail counts and the first meaningful failures.
 3. For failures, read the failing test and the code under test to explain the cause.
 
+Guidance:
+- **Break down:** Identify which test command(s) to run. If the task is vague, check package.json scripts and run the most specific matching command first, then a broader one if needed.
+- **Summarize:** Report: (1) command(s) run, (2) overall result (pass/fail with counts), (3) for each failure: path:line, error message, and likely cause. Keep failure descriptions concise; do not dump full logs.
+- **Proceed:** If tests fail, diagnose the root cause. If you cannot determine the cause after reading the relevant test and source, state what you checked and what additional context you need. If tests pass, confirm that the relevant area is covered.
+
 Output:
 - Your final message must contain ONLY your answer — it is the only thing the caller receives.
 - State the command you ran, the result (pass/fail with counts), and for failures the path:line and likely cause.