@hiai-gg/hiai-opencode 0.1.1 → 0.1.3

package/src/features/builtin-commands/templates/remove-ai-slops.ts

@@ -1,96 +1,96 @@
-export const REMOVE_AI_SLOPS_TEMPLATE = `# Remove AI Slops Command
-
-## What this command does
-Analyzes all files changed in the current branch (compared to parent commit), removes AI-generated code smells in parallel, then critically reviews the changes to ensure safety and behavior preservation. Fixes any issues found during review.
-
-## Step 0: Task Planning
-
-Use TodoWrite to create the task list:
-1. Get changed files from branch
-2. Run ai-slop-remover on each file in parallel
-3. Critically review all changes
-4. Fix any issues found
-
-## Role Definition
-You are a senior code quality engineer specialized in identifying and removing AI-generated code patterns while preserving original functionality. You have deep expertise in code review, refactoring safety, and behavioral preservation.
-
-## Process
-
-### Phase 1: Identify Changed Files
-Detect the repository base branch dynamically, then get all changed files in the current branch:
-\`\`\`bash
-BASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "main")
-git diff $(git merge-base "$BASE_BRANCH" HEAD)..HEAD --name-only
-\`\`\`
-
-If \`git symbolic-ref refs/remotes/origin/HEAD\` is unavailable, detect the base branch at runtime using the repo's configured remote default branch. Only fall back to \`main\` as a last resort.
-
-### Phase 2: Parallel AI Slop Removal
-For each changed file, spawn an agent in parallel using the Task tool with the ai-slop-remover skill:
-
-\`\`\`
-task(category="quick", load_skills=["ai-slop-remover"], run_in_background=true, description="Remove AI slops from {filename}", prompt="Remove AI slops from: {file_path}")
-\`\`\`
-
-**CRITICAL**: Launch ALL agents in a SINGLE message with multiple Task tool calls for maximum parallelism.
-
-Before running ai-slop-remover on each file, save a file-specific rollback artifact that captures only the delta introduced by the slop-removal pass. Use a safe pattern such as generating a per-file patch and reverse-applying it if review fails.
-
-Do NOT use \`git checkout -- {file_path}\` or any rollback that discards pre-existing branch changes in the file.
-
-### Phase 3: Critical Review
-After all ai-slop-remover agents complete, perform a critical review with the following checklist:
-
-**Safety Verification**:
-- [ ] No functional logic was accidentally removed
-- [ ] All error handling is preserved
-- [ ] Type hints remain correct and complete
-- [ ] Import statements are still valid
-- [ ] No breaking changes to public APIs
-
-**Behavior Preservation**:
-- [ ] Return values unchanged
-- [ ] Side effects unchanged
-- [ ] Exception behavior unchanged
-- [ ] Edge case handling preserved
-
-**Code Quality**:
-- [ ] Removed changes are genuinely AI slop (not intentional patterns)
-- [ ] Remaining code follows project conventions
-- [ ] No orphaned code or dead references
-
-### Phase 4: Fix Issues
-If any issues are found during critical review:
-1. Identify the specific problem
-2. Explain why it's a problem
-3. Revert only the ai-slop-remover delta using the saved per-file patch or an equivalent reverse-apply workflow
-4. If remaining ai-slops are found after reverting, remove them by editing the file yourself - with parallel tool calls, per-file
-5. Verify the fix doesn't introduce new issues
-
-## Output Format
-
-### Summary Report
-\`\`\`
-## AI Slop Removal Summary
-
-### Files Processed
-- file1.py: X changes
-- file2.py: Y changes
-
-### Critical Review Results
-- Safety: PASS/FAIL
-- Behavior: PASS/FAIL
-- Quality: PASS/FAIL
-
-### Issues Found & Fixed
-1. [Issue description] -> [Fix applied]
-
-### Final Status
-[CLEAN / ISSUES FIXED / REQUIRES ATTENTION]
-\`\`\`
-
-## Quality Assurance
-- NEVER remove code that serves a functional purpose
-- ALWAYS verify changes compile/parse correctly
-- ALWAYS preserve test coverage
-- If uncertain about a change, err on the side of keeping the original code`
+export const REMOVE_AI_SLOPS_TEMPLATE = `# Remove AI Slops Command
+
+## What this command does
+Analyzes all files changed in the current branch (compared to parent commit), removes AI-generated code smells in parallel, then critically reviews the changes to ensure safety and behavior preservation. Fixes any issues found during review.
+
+## Step 0: Task Planning
+
+Use TodoWrite to create the task list:
+1. Get changed files from branch
+2. Run ai-slop-remover on each file in parallel
+3. Critically review all changes
+4. Fix any issues found
+
+## Role Definition
+You are a senior code quality engineer specialized in identifying and removing AI-generated code patterns while preserving original functionality. You have deep expertise in code review, refactoring safety, and behavioral preservation.
+
+## Process
+
+### Phase 1: Identify Changed Files
+Detect the repository base branch dynamically, then get all changed files in the current branch:
+\`\`\`bash
+BASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "main")
+git diff $(git merge-base "$BASE_BRANCH" HEAD)..HEAD --name-only
+\`\`\`
+
+If \`git symbolic-ref refs/remotes/origin/HEAD\` is unavailable, detect the base branch at runtime using the repo's configured remote default branch. Only fall back to \`main\` as a last resort.
+
+### Phase 2: Parallel AI Slop Removal
+For each changed file, spawn an agent in parallel using the Task tool with the ai-slop-remover skill:
+
+\`\`\`
+task(category="quick", load_skills=["ai-slop-remover"], run_in_background=true, description="Remove AI slops from {filename}", prompt="Remove AI slops from: {file_path}")
+\`\`\`
+
+**CRITICAL**: Launch ALL agents in a SINGLE message with multiple Task tool calls for maximum parallelism.
+
+Before running ai-slop-remover on each file, save a file-specific rollback artifact that captures only the delta introduced by the slop-removal pass. Use a safe pattern such as generating a per-file patch and reverse-applying it if review fails.
+
+Do NOT use \`git checkout -- {file_path}\` or any rollback that discards pre-existing branch changes in the file.
+
+### Phase 3: Critical Review
+After all ai-slop-remover agents complete, perform a critical review with the following checklist:
+
+**Safety Verification**:
+- [ ] No functional logic was accidentally removed
+- [ ] All error handling is preserved
+- [ ] Type hints remain correct and complete
+- [ ] Import statements are still valid
+- [ ] No breaking changes to public APIs
+
+**Behavior Preservation**:
+- [ ] Return values unchanged
+- [ ] Side effects unchanged
+- [ ] Exception behavior unchanged
+- [ ] Edge case handling preserved
+
+**Code Quality**:
+- [ ] Removed changes are genuinely AI slop (not intentional patterns)
+- [ ] Remaining code follows project conventions
+- [ ] No orphaned code or dead references
+
+### Phase 4: Fix Issues
+If any issues are found during critical review:
+1. Identify the specific problem
+2. Explain why it's a problem
+3. Revert only the ai-slop-remover delta using the saved per-file patch or an equivalent reverse-apply workflow
+4. If remaining ai-slops are found after reverting, remove them by editing the file yourself - with parallel tool calls, per-file
+5. Verify the fix doesn't introduce new issues
+
+## Output Format
+
+### Summary Report
+\`\`\`
+## AI Slop Removal Summary
+
+### Files Processed
+- file1.py: X changes
+- file2.py: Y changes
+
+### Critical Review Results
+- Safety: PASS/FAIL
+- Behavior: PASS/FAIL
+- Quality: PASS/FAIL
+
+### Issues Found & Fixed
+1. [Issue description] -> [Fix applied]
+
+### Final Status
+[CLEAN / ISSUES FIXED / REQUIRES ATTENTION]
+\`\`\`
+
+## Quality Assurance
+- NEVER remove code that serves a functional purpose
+- ALWAYS verify changes compile/parse correctly
+- ALWAYS preserve test coverage
+- If uncertain about a change, err on the side of keeping the original code`

package/src/features/builtin-commands/templates/start-work.ts

@@ -1,128 +1,128 @@
-export const START_WORK_TEMPLATE = `You are starting a Bob work session.
-
-## ARGUMENTS
-
-- \`/start-work [plan-name] [--worktree <path>]\`
-  - \`plan-name\` (optional): name or partial match of the plan to start
-  - \`--worktree <path>\` (optional): absolute path to an existing git worktree to work in
-    - If specified and valid: hook pre-sets worktree_path in boulder.json
-    - If specified but invalid: you must run \`git worktree add <path> <branch>\` first
-    - If omitted: work directly in the current project directory (no worktree)
-
-## WHAT TO DO
-
-1. **Find available plans**: Search for Strategist-generated plan files at \`.bob/plans/\`
-
-2. **Check for active boulder state**: Read \`.bob/boulder.json\` if it exists
-
-3. **Decision logic**:
-   - If \`.bob/boulder.json\` exists AND plan is NOT complete (has unchecked boxes):
-     - **APPEND** current session to session_ids
-     - Continue work on existing plan
-   - If no active plan OR plan is complete:
-     - List available plan files
-     - If ONE plan: auto-select it
-     - If MULTIPLE plans: show list with timestamps, ask user to select
-
-4. **Worktree Setup** (ONLY when \`--worktree\` was explicitly specified and \`worktree_path\` not already set in boulder.json):
-   1. \`git worktree list --porcelain\` - see available worktrees
-   2. Create: \`git worktree add <absolute-path> <branch-or-HEAD>\`
-   3. Update boulder.json to add \`"worktree_path": "<absolute-path>"\`
-   4. All work happens inside that worktree directory
-
-5. **Create/Update boulder.json**:
-   \`\`\`json
-   {
-     "active_plan": "/absolute/path/to/plan.md",
-     "started_at": "ISO_TIMESTAMP",
-     "session_ids": ["session_id_1", "session_id_2"],
-     "plan_name": "plan-name",
-     "worktree_path": "/absolute/path/to/git/worktree"
-   }
-   \`\`\`
-
-6. **Read the plan file** and start executing tasks according to guard workflow
-
-## OUTPUT FORMAT
-
-When listing plans for selection:
-\`\`\`
-Available Work Plans
-
-Current Time: {ISO timestamp}
-Session ID: {current session id}
-
-1. [plan-name-1.md] - Modified: {date} - Progress: 3/10 tasks
-2. [plan-name-2.md] - Modified: {date} - Progress: 0/5 tasks
-
-Which plan would you like to work on? (Enter number or plan name)
-\`\`\`
-
-When resuming existing work:
-\`\`\`
-Resuming Work Session
-
-Active Plan: {plan-name}
-Progress: {completed}/{total} tasks
-Sessions: {count} (appending current session)
-Worktree: {worktree_path}
-
-Reading plan and continuing from last incomplete task...
-\`\`\`
-
-When auto-selecting single plan:
-\`\`\`
-Starting Work Session
-
-Plan: {plan-name}
-Session ID: {session_id}
-Started: {timestamp}
-Worktree: {worktree_path}
-
-Reading plan and beginning execution...
-\`\`\`
-
-## CRITICAL
-
-- The session_id is injected by the hook - use it directly
-- Always update boulder.json BEFORE starting work
-- If worktree_path is set in boulder.json, all work happens inside that worktree directory
-- Read the FULL plan file before delegating any tasks
-- Follow guard delegation protocols (7-section format)
-
-## TASK BREAKDOWN (MANDATORY)
-
-After reading the plan file, you MUST decompose every plan task into granular, implementation-level sub-steps and register ALL of them as task/todo items BEFORE starting any work.
-
-**How to break down**:
-- Each plan checkbox item (e.g., \`- [ ] Add user authentication\`) must be split into concrete, actionable sub-tasks
-- Sub-tasks should be specific enough that each one touches a clear set of files/functions
-- Include: file to modify, what to change, expected behavior, and how to verify
-- Do NOT leave any task vague - "implement feature X" is NOT acceptable; "add validateToken() to src/auth/middleware.ts that checks JWT expiry and returns 401" IS acceptable
-
-**Example breakdown**:
-Plan task: \`- [ ] Add rate limiting to API\`
-→ Todo items:
-  1. Create \`src/middleware/rate-limiter.ts\` with sliding window algorithm (max 100 req/min per IP)
-  2. Add RateLimiter middleware to \`src/app.ts\` router chain, before auth middleware
-  3. Add rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining) to response in \`rate-limiter.ts\`
-  4. Add test: verify 429 response after exceeding limit in \`src/middleware/rate-limiter.test.ts\`
-  5. Add test: verify headers are present on normal responses
-
-Register these as task/todo items so progress is tracked and visible throughout the session.
-
-## WORKTREE COMPLETION
-
-When working in a worktree (\`worktree_path\` is set in boulder.json) and ALL plan tasks are complete:
-1. Commit all remaining changes in the worktree
-2. **Sync .bob state back**: Copy \`.bob/\` from the worktree to the main repo before removal.
-   This is CRITICAL when \`.bob/\` is gitignored - state written during worktree execution would otherwise be lost.
-   \`\`\`bash
-   cp -r <worktree-path>/.bob/* <main-repo>/.bob/ 2>/dev/null || true
-   \`\`\`
-3. Switch to the main working directory (the original repo, NOT the worktree)
-4. Merge the worktree branch into the current branch: \`git merge <worktree-branch>\`
-5. If merge succeeds, clean up: \`git worktree remove <worktree-path>\`
-6. Remove the boulder.json state
-
-This is the DEFAULT behavior when \`--worktree\` was used. Skip merge only if the user explicitly instructs otherwise (e.g., asks to create a PR instead).`
+export const START_WORK_TEMPLATE = `You are starting a Bob work session.
+
+## ARGUMENTS
+
+- \`/start-work [plan-name] [--worktree <path>]\`
+  - \`plan-name\` (optional): name or partial match of the plan to start
+  - \`--worktree <path>\` (optional): absolute path to an existing git worktree to work in
+    - If specified and valid: hook pre-sets worktree_path in boulder.json
+    - If specified but invalid: you must run \`git worktree add <path> <branch>\` first
+    - If omitted: work directly in the current project directory (no worktree)
+
+## WHAT TO DO
+
+1. **Find available plans**: Search for Strategist-generated plan files at \`.bob/plans/\`
+
+2. **Check for active boulder state**: Read \`.bob/boulder.json\` if it exists
+
+3. **Decision logic**:
+   - If \`.bob/boulder.json\` exists AND plan is NOT complete (has unchecked boxes):
+     - **APPEND** current session to session_ids
+     - Continue work on existing plan
+   - If no active plan OR plan is complete:
+     - List available plan files
+     - If ONE plan: auto-select it
+     - If MULTIPLE plans: show list with timestamps, ask user to select
+
+4. **Worktree Setup** (ONLY when \`--worktree\` was explicitly specified and \`worktree_path\` not already set in boulder.json):
+   1. \`git worktree list --porcelain\` - see available worktrees
+   2. Create: \`git worktree add <absolute-path> <branch-or-HEAD>\`
+   3. Update boulder.json to add \`"worktree_path": "<absolute-path>"\`
+   4. All work happens inside that worktree directory
+
+5. **Create/Update boulder.json**:
+   \`\`\`json
+   {
+     "active_plan": "/absolute/path/to/plan.md",
+     "started_at": "ISO_TIMESTAMP",
+     "session_ids": ["session_id_1", "session_id_2"],
+     "plan_name": "plan-name",
+     "worktree_path": "/absolute/path/to/git/worktree"
+   }
+   \`\`\`
+
+6. **Read the plan file** and start executing tasks according to guard workflow
+
+## OUTPUT FORMAT
+
+When listing plans for selection:
+\`\`\`
+Available Work Plans
+
+Current Time: {ISO timestamp}
+Session ID: {current session id}
+
+1. [plan-name-1.md] - Modified: {date} - Progress: 3/10 tasks
+2. [plan-name-2.md] - Modified: {date} - Progress: 0/5 tasks
+
+Which plan would you like to work on? (Enter number or plan name)
+\`\`\`
+
+When resuming existing work:
+\`\`\`
+Resuming Work Session
+
+Active Plan: {plan-name}
+Progress: {completed}/{total} tasks
+Sessions: {count} (appending current session)
+Worktree: {worktree_path}
+
+Reading plan and continuing from last incomplete task...
+\`\`\`
+
+When auto-selecting single plan:
+\`\`\`
+Starting Work Session
+
+Plan: {plan-name}
+Session ID: {session_id}
+Started: {timestamp}
+Worktree: {worktree_path}
+
+Reading plan and beginning execution...
+\`\`\`
+
+## CRITICAL
+
+- The session_id is injected by the hook - use it directly
+- Always update boulder.json BEFORE starting work
+- If worktree_path is set in boulder.json, all work happens inside that worktree directory
+- Read the FULL plan file before delegating any tasks
+- Follow guard delegation protocols (7-section format)
+
+## TASK BREAKDOWN (MANDATORY)
+
+After reading the plan file, you MUST decompose every plan task into granular, implementation-level sub-steps and register ALL of them as task/todo items BEFORE starting any work.
+
+**How to break down**:
+- Each plan checkbox item (e.g., \`- [ ] Add user authentication\`) must be split into concrete, actionable sub-tasks
+- Sub-tasks should be specific enough that each one touches a clear set of files/functions
+- Include: file to modify, what to change, expected behavior, and how to verify
+- Do NOT leave any task vague - "implement feature X" is NOT acceptable; "add validateToken() to src/auth/middleware.ts that checks JWT expiry and returns 401" IS acceptable
+
+**Example breakdown**:
+Plan task: \`- [ ] Add rate limiting to API\`
+→ Todo items:
+  1. Create \`src/middleware/rate-limiter.ts\` with sliding window algorithm (max 100 req/min per IP)
+  2. Add RateLimiter middleware to \`src/app.ts\` router chain, before auth middleware
+  3. Add rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining) to response in \`rate-limiter.ts\`
+  4. Add test: verify 429 response after exceeding limit in \`src/middleware/rate-limiter.test.ts\`
+  5. Add test: verify headers are present on normal responses
+
+Register these as task/todo items so progress is tracked and visible throughout the session.
+
+## WORKTREE COMPLETION
+
+When working in a worktree (\`worktree_path\` is set in boulder.json) and ALL plan tasks are complete:
+1. Commit all remaining changes in the worktree
+2. **Sync .bob state back**: Copy \`.bob/\` from the worktree to the main repo before removal.
+   This is CRITICAL when \`.bob/\` is gitignored - state written during worktree execution would otherwise be lost.
+   \`\`\`bash
+   cp -r <worktree-path>/.bob/* <main-repo>/.bob/ 2>/dev/null || true
+   \`\`\`
+3. Switch to the main working directory (the original repo, NOT the worktree)
+4. Merge the worktree branch into the current branch: \`git merge <worktree-branch>\`
+5. If merge succeeds, clean up: \`git worktree remove <worktree-path>\`
+6. Remove the boulder.json state
+
+This is the DEFAULT behavior when \`--worktree\` was used. Skip merge only if the user explicitly instructs otherwise (e.g., asks to create a PR instead).`

package/src/features/builtin-commands/templates/stop-continuation.ts

@@ -1,13 +1,13 @@
-export const STOP_CONTINUATION_TEMPLATE = `Stop all continuation mechanisms for the current session.
-
-This command will:
-1. Stop the todo-continuation-enforcer from automatically continuing incomplete tasks
-2. Cancel any active Ralph Loop
-3. Clear the boulder state for the current project
-
-After running this command:
-- The session will not auto-continue when idle
-- You can manually continue work when ready
-- The stop state is per-session and clears when the session ends
-
-Use this when you need to pause automated continuation and take manual control.`
+export const STOP_CONTINUATION_TEMPLATE = `Stop all continuation mechanisms for the current session.
+
+This command will:
+1. Stop the todo-continuation-enforcer from automatically continuing incomplete tasks
+2. Cancel any active Ralph Loop
+3. Clear the boulder state for the current project
+
+After running this command:
+- The session will not auto-continue when idle
+- You can manually continue work when ready
+- The stop state is per-session and clears when the session ends
+
+Use this when you need to pause automated continuation and take manual control.`

package/src/features/builtin-commands/types.ts

@@ -1,9 +1,9 @@
-import type { CommandDefinition } from "../claude-code-command-loader"
-
-export type BuiltinCommandName = "init-deep" | "ralph-loop" | "cancel-ralph" | "ulw-loop" | "refactor" | "start-work" | "stop-continuation" | "handoff" | "remove-ai-slops"
-
-export interface BuiltinCommandConfig {
-  disabled_commands?: BuiltinCommandName[]
-}
-
-export type BuiltinCommands = Record<string, CommandDefinition>
+import type { CommandDefinition } from "../claude-code-command-loader"
+
+export type BuiltinCommandName = "init-deep" | "ralph-loop" | "cancel-ralph" | "ulw-loop" | "refactor" | "start-work" | "stop-continuation" | "handoff" | "remove-ai-slops"
+
+export interface BuiltinCommandConfig {
+  disabled_commands?: BuiltinCommandName[]
+}
+
+export type BuiltinCommands = Record<string, CommandDefinition>

package/src/features/builtin-skills/index.ts

@@ -1,2 +1,2 @@
-export * from "./types"
-export { createBuiltinSkills, type CreateBuiltinSkillsOptions } from "./skills"
+export * from "./types"
+export { createBuiltinSkills, type CreateBuiltinSkillsOptions } from "./skills"