oh-my-opencode 4.10.0 → 4.11.0

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

@@ -1,2 +1,2 @@
-export declare const REMOVE_AI_SLOPS_TEMPLATE = "# Remove AI Slops Command\n\n## Codex Harness Tool Compatibility\n\nThis command includes examples for the OpenCode harness. In Codex, do not call OpenCode-only tools such as `call_omo_agent(...)`, `task(...)`, `background_output(...)`, or `team_*(...)` literally. Translate those examples to Codex native tools:\n\n| OpenCode example | Codex tool to use |\n| --- | --- |\n| `call_omo_agent(subagent_type=\"explore\", ...)` | `spawn_agent(agent_type=\"explorer\", task_name=\"...\", message=\"...\")` |\n| `call_omo_agent(subagent_type=\"librarian\", ...)` | `spawn_agent(agent_type=\"librarian\", task_name=\"...\", message=\"...\")` |\n| `task(subagent_type=\"plan\", ...)` | `spawn_agent(agent_type=\"plan\", task_name=\"...\", message=\"...\")` |\n| `task(subagent_type=\"oracle\", ...)` | `spawn_agent(agent_type=\"codex-ultrawork-reviewer\", task_name=\"...\", message=\"...\")` |\n| `task(category=\"...\", ...)` | `spawn_agent(agent_type=\"worker\", task_name=\"...\", message=\"...\")` |\n| `background_output(task_id=\"...\")` | `wait_agent(...)` to wait for subagent completion and mailbox updates |\n| `team_*(...)` | Use Codex native subagents plus `send_message`, `followup_task`, `wait_agent`, and `close_agent` |\n\nWhen translating `load_skills=[...]`, include the requested skill names in the spawned agent's `message`. If a code block below conflicts with this section, this section wins.\n\n## What this command does\nAnalyzes 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.\n\n## Step 0: Task Planning\n\nUse TodoWrite to create the task list:\n1. Get changed files from branch\n2. Run $omo:remove-ai-slops on each file in parallel\n3. Critically review all changes\n4. Fix any issues found\n\n## Role Definition\nYou 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.\n\n## Process\n\n### Phase 1: Identify Changed Files\nDetect the repository base branch dynamically, then get all changed files in the current branch:\n```bash\nBASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo \"main\")\ngit diff $(git merge-base \"$BASE_BRANCH\" HEAD)..HEAD --name-only\n```\n\nIf `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.\n\n### Phase 2: Parallel AI Slop Removal\nFor each changed file, spawn an agent in parallel using the Task tool with the $omo:remove-ai-slops skill:\n\n```\ntask(category=\"quick\", load_skills=[\"remove-ai-slops\"], run_in_background=true, description=\"Remove AI slops from {filename}\", prompt=\"Remove AI slops from: {file_path}\")\n```\n\n**CRITICAL**: Launch ALL agents in a SINGLE message with multiple Task tool calls for maximum parallelism.\n\nBefore running $omo:remove-ai-slops 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.\n\nDo NOT use `git checkout -- {file_path}` or any rollback that discards pre-existing branch changes in the file.\n\n### Phase 3: Critical Review\nAfter all $omo:remove-ai-slops agents complete, perform a critical review with the following checklist:\n\n**Safety Verification**:\n- [ ] No functional logic was accidentally removed\n- [ ] All error handling is preserved\n- [ ] Type hints remain correct and complete\n- [ ] Import statements are still valid\n- [ ] No breaking changes to public APIs\n\n**Behavior Preservation**:\n- [ ] Return values unchanged\n- [ ] Side effects unchanged\n- [ ] Exception behavior unchanged\n- [ ] Edge case handling preserved\n\n**Code Quality**:\n- [ ] Removed changes are genuinely AI slop (not intentional patterns)\n- [ ] Remaining code follows project conventions\n- [ ] No orphaned code or dead references\n\n### Phase 4: Fix Issues\nIf any issues are found during critical review:\n1. Identify the specific problem\n2. Explain why it's a problem\n3. Revert only the $omo:remove-ai-slops delta using the saved per-file patch or an equivalent reverse-apply workflow\n4. If remaining ai-slops are found after reverting, remove them by editing the file yourself - with parallel tool calls, per-file\n5. Verify the fix doesn't introduce new issues\n\n## Output Format\n\n### Summary Report\n```\n## AI Slop Removal Summary\n\n### Files Processed\n- file1.py: X changes\n- file2.py: Y changes\n\n### Critical Review Results\n- Safety: PASS/FAIL\n- Behavior: PASS/FAIL\n- Quality: PASS/FAIL\n\n### Issues Found & Fixed\n1. [Issue description] -> [Fix applied]\n\n### Final Status\n[CLEAN / ISSUES FIXED / REQUIRES ATTENTION]\n```\n\n## Quality Assurance\n- NEVER remove code that serves a functional purpose\n- ALWAYS verify changes compile/parse correctly\n- ALWAYS preserve test coverage\n- If uncertain about a change, err on the side of keeping the original code";
+export declare const REMOVE_AI_SLOPS_TEMPLATE = "# Remove AI Slops Command\n\n## Codex Harness Tool Compatibility\n\nThis command includes examples for the OpenCode harness. In Codex, do not call OpenCode-only tools such as `call_omo_agent(...)`, `task(...)`, `background_output(...)`, or `team_*(...)` literally. Translate those examples to Codex native tools:\n\n| OpenCode example | Codex tool to use |\n| --- | --- |\n| `call_omo_agent(subagent_type=\"explore\", ...)` | `spawn_agent(agent_type=\"explorer\", task_name=\"...\", message=\"...\")` |\n| `call_omo_agent(subagent_type=\"librarian\", ...)` | `spawn_agent(agent_type=\"librarian\", task_name=\"...\", message=\"...\")` |\n| `task(subagent_type=\"plan\", ...)` | `spawn_agent(agent_type=\"plan\", task_name=\"...\", message=\"...\")` |\n| `task(subagent_type=\"oracle\", ...)` | `multi_agent_v1.spawn_agent({\"message\":\"TASK: act as a rigorous reviewer. ...\",\"agent_type\":\"lazycodex-gate-reviewer\",\"fork_context\":false})` |\n| `task(category=\"...\", ...)` | `spawn_agent(agent_type=\"worker\", task_name=\"...\", message=\"...\")` |\n| `background_output(task_id=\"...\")` | `wait_agent(...)` to wait for subagent completion and mailbox updates |\n| `team_*(...)` | Use Codex native subagents plus `send_message`, `followup_task`, `wait_agent`, and `close_agent` |\n\nWhen translating `load_skills=[...]`, include the requested skill names in the spawned agent's `message`. If a code block below conflicts with this section, this section wins.\n\n## What this command does\nAnalyzes 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.\n\n## Step 0: Task Planning\n\nUse TodoWrite to create the task list:\n1. Get changed files from branch\n2. Run $omo:remove-ai-slops on each file in parallel\n3. Critically review all changes\n4. Fix any issues found\n\n## Role Definition\nYou 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.\n\n## Process\n\n### Phase 1: Identify Changed Files\nDetect the repository base branch dynamically, then get all changed files in the current branch:\n```bash\nBASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo \"main\")\ngit diff $(git merge-base \"$BASE_BRANCH\" HEAD)..HEAD --name-only\n```\n\nIf `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.\n\n### Phase 2: Parallel AI Slop Removal\nFor each changed file, spawn an agent in parallel using the Task tool with the $omo:remove-ai-slops skill:\n\n```\ntask(category=\"quick\", load_skills=[\"remove-ai-slops\"], run_in_background=true, description=\"Remove AI slops from {filename}\", prompt=\"Remove AI slops from: {file_path}\")\n```\n\n**CRITICAL**: Launch ALL agents in a SINGLE message with multiple Task tool calls for maximum parallelism.\n\nBefore running $omo:remove-ai-slops 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.\n\nDo NOT use `git checkout -- {file_path}` or any rollback that discards pre-existing branch changes in the file.\n\n### Phase 3: Critical Review\nAfter all $omo:remove-ai-slops agents complete, perform a critical review with the following checklist:\n\n**Safety Verification**:\n- [ ] No functional logic was accidentally removed\n- [ ] All error handling is preserved\n- [ ] Type hints remain correct and complete\n- [ ] Import statements are still valid\n- [ ] No breaking changes to public APIs\n\n**Behavior Preservation**:\n- [ ] Return values unchanged\n- [ ] Side effects unchanged\n- [ ] Exception behavior unchanged\n- [ ] Edge case handling preserved\n\n**Code Quality**:\n- [ ] Removed changes are genuinely AI slop (not intentional patterns)\n- [ ] Remaining code follows project conventions\n- [ ] No orphaned code or dead references\n\n### Phase 4: Fix Issues\nIf any issues are found during critical review:\n1. Identify the specific problem\n2. Explain why it's a problem\n3. Revert only the $omo:remove-ai-slops delta using the saved per-file patch or an equivalent reverse-apply workflow\n4. If remaining ai-slops are found after reverting, remove them by editing the file yourself - with parallel tool calls, per-file\n5. Verify the fix doesn't introduce new issues\n\n## Output Format\n\n### Summary Report\n```\n## AI Slop Removal Summary\n\n### Files Processed\n- file1.py: X changes\n- file2.py: Y changes\n\n### Critical Review Results\n- Safety: PASS/FAIL\n- Behavior: PASS/FAIL\n- Quality: PASS/FAIL\n\n### Issues Found & Fixed\n1. [Issue description] -> [Fix applied]\n\n### Final Status\n[CLEAN / ISSUES FIXED / REQUIRES ATTENTION]\n```\n\n## Quality Assurance\n- NEVER remove code that serves a functional purpose\n- ALWAYS verify changes compile/parse correctly\n- ALWAYS preserve test coverage\n- If uncertain about a change, err on the side of keeping the original code";
 export declare const REMOVE_AI_SLOPS_TEAM_MODE_ADDENDUM = "\n---\n\n# Team Mode Protocol (active when team_* tools are present)\n\nTeam mode is enabled for this session. The rules below **override Phase 2-4** of the legacy flow above. Follow this protocol instead of the per-file fire-and-forget `task()` dispatch.\n\n## Phase 2 (team): `slop-squad` setup\n\n**Precondition checks** (fail hard if any step fails):\n\n1. Load the `team-mode` skill via the `skill` tool for lifecycle, message protocol, broadcast rules, 32KB message cap, and 4 parallel worker cap.\n2. Call `team_list` and verify no active run named `slop-squad` exists. If one does, it is an orphan from a crashed prior session \u2014 `team_shutdown_request` + `team_approve_shutdown` + `team_delete` it before proceeding. Do not rename the team or run concurrent sessions under the same name.\n3. If `~/.omo/teams/slop-squad/config.json` is missing, write it using the spec below.\n\n**Team spec** (`~/.omo/teams/slop-squad/config.json`):\n\n```json\n{\n  \"name\": \"slop-squad\",\n  \"lead\": { \"kind\": \"subagent_type\", \"subagent_type\": \"sisyphus\" },\n  \"members\": [\n    {\n      \"kind\": \"category\",\n      \"category\": \"quick\",\n      \"prompt\": \"You run $omo:remove-ai-slops on ONE file per task. Load $omo:remove-ai-slops via the skill tool. Read the task description for the file path. Apply the skill's detection criteria verbatim. After edits: run lsp_diagnostics on the file. Report via team_send_message(teamRunId=<id>, to=\"lead\", summary=<change count>, body=<full $omo:remove-ai-slops report>) + team_task_update(status=completed). On ambiguity: send team_send_message(teamRunId=<id>, to=\"lead\", summary=\"UNCLEAR\", body=<reason>) + team_task_update(status=pending). Never git add, never run tests, never touch other files.\"\n    },\n    { \"kind\": \"category\", \"category\": \"quick\", \"prompt\": \"Same contract as peer quick worker.\" },\n    { \"kind\": \"category\", \"category\": \"quick\", \"prompt\": \"Same contract as peer quick worker.\" },\n    {\n      \"kind\": \"category\",\n      \"category\": \"unspecified-low\",\n      \"prompt\": \"You are the FIX worker. You claim rework tasks that the lead creates after the external reviewer flags issues. Read the reviewer's per-hunk rollback instructions in the task description, apply the reverse patch, then run $omo:remove-ai-slops ONLY on the non-rolled-back remainder. Same reporting contract as quick peers. Handle UNCLEAR escalations the same way.\"\n    }\n  ]\n}\n```\n\nRationale for this composition:\n- **4 workers = team mode's parallel cap.** A fifth member just queues.\n- **Reviewer is NOT a team member** \u2014 review demands stronger reasoning than category routing provides (team category members are downcast to sisyphus-junior). The reviewer runs OUTSIDE the team as a `deep` task; see Phase 3.\n- **quick \u00D7 3** absorbs the mass of per-file slop removal. **unspecified-low \u00D7 1** is the rework lane for fixes triggered by reviewer findings.\n\n**Team lifecycle** (create once, reuse until Phase 5 cleanup):\n\n1. `team_create(teamName=\"slop-squad\")`. Record `teamRunId` \u2014 every subsequent team call needs it.\n2. Broadcast the detection criteria ONCE so each task description stays minimal:\n   ```\n   team_send_message(\n     teamRunId=<id>, to=\"*\", kind=\"announcement\",\n     summary=\"slop-criteria\",\n     body=<the 9 slop categories + KEEP rules; reference the $omo:remove-ai-slops skill content>\n   )\n   ```\n3. Before spawning tasks, save a per-file rollback artifact that captures only the delta the slop-removal pass will introduce. Do NOT use `git checkout -- <file>` \u2014 that would discard pre-existing branch changes.\n4. For each changed file, `team_task_create(teamRunId=<id>, subject=\"slop: <file>\", description=<file path + rollback artifact path + reporting format>, blockedBy=[])`.\n\n## Phase 3 (team): Incremental reviewer dispatch\n\nWhile any team task is `pending | claimed | in_progress`:\n\n- Wait for `<system-reminder>` or member messages. Do NOT tight-poll `team_status`; the runtime notifies on state changes. A single `team_status` check is acceptable if no notification arrives within roughly 10 seconds of expected completion.\n- On each worker completion report:\n  - Log the report to the pending final summary (no blocking).\n  - Immediately dispatch an **external reviewer** \u2014 review runs OUTSIDE the team because team-member category routing downcasts to sisyphus-junior:\n    ```\n    task(\n      category=\"deep\",\n      load_skills=[],\n      run_in_background=true,\n      description=\"slop review: <file>\",\n      prompt=<file path + full worker report + Safety/Behavior/Quality checklist + instruction to output \"PASS\" or \"FAIL:<per-hunk rollback instructions>\">\n    )\n    ```\n    If `deep` is unavailable in this session, fall back to `category=\"unspecified-high\"`.\n- On a reviewer task returning FAIL:\n  - Create a rework team task: `team_task_create(subject=\"rework: <file>\", description=<reverse-patch hunks from reviewer + \"then run $omo:remove-ai-slops on remaining non-rolled-back issues only\">)`. The `unspecified-low` fix member claims it.\n  - Create a new reviewer task paired to the rework completion (same incremental pattern).\n- Loop until every file has a PASS from the reviewer AND no team task is outstanding.\n\n## Phase 4 (team): Fix issues\n\nFixes happen incrementally during Phase 3's loop via rework tasks \u2014 this phase is already handled when the loop exits. Any remaining manual fix that neither worker nor fix member could resolve is handled by Lead here, editing files directly.\n\n## Phase 5 (team): Team cleanup\n\nBefore producing the summary report, dismantle the team on EVERY exit path \u2014 success, escalation, abort \u2014 otherwise the next session's Phase 2 precondition check catches the orphan.\n\n1. `team_shutdown_request` for each member, then `team_approve_shutdown` if members do not self-approve within a reasonable window.\n2. `team_delete(teamRunId=<id>)`.\n3. `team_list` to confirm no residual `slop-squad` run.\n\nThe `~/.omo/teams/slop-squad/config.json` declaration file stays on disk; it is reused next session.\n\n## MUST NOT (team mode)\n\n- Lead never edits files directly \u2014 orchestrate only. If editing is needed, it goes into a team task.\n- Do not inline the full slop-criteria into every task description; rely on the Phase 2 broadcast.\n- Do not call `team_create` again mid-session. One team per resolution.\n- Do not put `oracle` / `librarian` into the team spec \u2014 they are team-ineligible; call them via `task()` outside the team when needed.\n";

package/dist/features/builtin-skills/index.d.ts

@@ -1,2 +1 @@
-export * from "./types";
-export { createBuiltinSkills, resolveActiveBuiltinSkills, type CreateBuiltinSkillsOptions, type ResolveActiveBuiltinSkillsOptions, } from "./skills";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/index";

package/dist/features/builtin-skills/skill-file-loader.d.ts

@@ -1,4 +1 @@
-type SkillFileReader = (path: string, encoding: "utf8") => string;
-export declare function createSharedSkillTemplateLoader(readFile?: SkillFileReader, baseDir?: string): (skillName: string) => string;
-export declare function loadSharedSkillTemplate(skillName: string): string;
-export {};
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skill-file-loader";

package/dist/features/builtin-skills/skills/agent-browser-skill.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const agentBrowserSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/agent-browser-skill";

package/dist/features/builtin-skills/skills/agent-browser-template.d.ts

@@ -1,2 +1 @@
-export declare function createAgentBrowserTemplate(markdown: string): string;
-export declare const agentBrowserTemplate: string;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/agent-browser-template";

package/dist/features/builtin-skills/skills/debugging.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const debuggingSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/debugging";

package/dist/features/builtin-skills/skills/dev-browser.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const devBrowserSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/dev-browser";

package/dist/features/builtin-skills/skills/frontend.d.ts

@@ -0,0 +1 @@
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/frontend";

package/dist/features/builtin-skills/skills/git-master-sections/commit-atomic-planning.d.ts

@@ -1 +1 @@
-export declare const GIT_MASTER_COMMIT_ATOMIC_PLANNING_SECTION = "## PHASE 3: Atomic Unit Planning (BLOCKING - MUST OUTPUT BEFORE PROCEEDING)\n\n<atomic_planning>\n**THIS PHASE HAS MANDATORY OUTPUT** - You MUST print the commit plan before moving to Phase 4.\n\n### 3.0 Calculate Minimum Commit Count FIRST\n\n```\nFORMULA: min_commits = ceil(file_count / 3)\n\n 3 files -> min 1 commit\n 5 files -> min 2 commits\n 9 files -> min 3 commits\n15 files -> min 5 commits\n```\n\n**If your planned commit count < min_commits -> WRONG. SPLIT MORE.**\n\n### 3.1 Split by Directory/Module FIRST (Primary Split)\n\n**RULE: Different directories = Different commits (almost always)**\n\n```\nExample: 8 changed files\n  - app/[locale]/page.tsx\n  - app/[locale]/layout.tsx\n  - components/demo/browser-frame.tsx\n  - components/demo/shopify-full-site.tsx\n  - components/pricing/pricing-table.tsx\n  - e2e/navbar.spec.ts\n  - messages/en.json\n  - messages/ko.json\n\nWRONG: 1 commit \"Update landing page\" (LAZY, WRONG)\nWRONG: 2 commits (still too few)\n\nCORRECT: Split by directory/concern:\n  - Commit 1: app/[locale]/page.tsx + layout.tsx (app layer)\n  - Commit 2: components/demo/* (demo components)\n  - Commit 3: components/pricing/* (pricing components)\n  - Commit 4: e2e/* (tests)\n  - Commit 5: messages/* (i18n)\n  = 5 commits from 8 files (CORRECT)\n```\n\n### 3.2 Split by Concern SECOND (Secondary Split)\n\n**Within same directory, split by logical concern:**\n\n```\nExample: components/demo/ has 4 files\n  - browser-frame.tsx (UI frame)\n  - shopify-full-site.tsx (specific demo)\n  - review-dashboard.tsx (NEW - specific demo)\n  - tone-settings.tsx (NEW - specific demo)\n\nOption A (acceptable): 1 commit if ALL tightly coupled\nOption B (preferred): 2 commits\n  - Commit: \"Update existing demo components\" (browser-frame, shopify)\n  - Commit: \"Add new demo components\" (review-dashboard, tone-settings)\n```\n\n### 3.3 NEVER Do This (Anti-Pattern Examples)\n\n```\nWRONG: \"Refactor entire landing page\" - 1 commit with 15 files\nWRONG: \"Update components and tests\" - 1 commit mixing concerns\nWRONG: \"Big update\" - Any commit touching 5+ unrelated files\n\nRIGHT: Multiple focused commits, each 1-4 files max\nRIGHT: Each commit message describes ONE specific change\nRIGHT: A reviewer can understand each commit in 30 seconds\n```\n\n### 3.4 Implementation + Test Pairing (MANDATORY)\n\n```\nRULE: Test files MUST be in same commit as implementation\n\nTest patterns to match:\n- test_*.py <-> *.py\n- *_test.py <-> *.py\n- *.test.ts <-> *.ts\n- *.spec.ts <-> *.ts\n- __tests__/*.ts <-> *.ts\n- tests/*.py <-> src/*.py\n```\n\n### 3.5 MANDATORY JUSTIFICATION (Before Creating Commit Plan)\n\n**NON-NEGOTIABLE: Before finalizing your commit plan, you MUST:**\n\n```\nFOR EACH planned commit with 3+ files:\n  1. List all files in this commit\n  2. Write ONE sentence explaining why they MUST be together\n  3. If you can't write that sentence -> SPLIT\n\nTEMPLATE:\n\"Commit N contains [files] because [specific reason they are inseparable].\"\n\nVALID reasons:\n  VALID: \"implementation file + its direct test file\"\n  VALID: \"type definition + the only file that uses it\"\n  VALID: \"migration + model change (would break without both)\"\n\nINVALID reasons (MUST SPLIT instead):\n  INVALID: \"all related to feature X\" (too vague)\n  INVALID: \"part of the same PR\" (not a reason)\n  INVALID: \"they were changed together\" (not a reason)\n  INVALID: \"makes sense to group\" (not a reason)\n```\n\n**OUTPUT THIS JUSTIFICATION in your analysis before executing commits.**\n\n### 3.7 Dependency Ordering\n\n```\nLevel 0: Utilities, constants, type definitions\nLevel 1: Models, schemas, interfaces\nLevel 2: Services, business logic\nLevel 3: API endpoints, controllers\nLevel 4: Configuration, infrastructure\n\nCOMMIT ORDER: Level 0 -> Level 1 -> Level 2 -> Level 3 -> Level 4\n```\n\n### 3.8 Create Commit Groups\n\nFor each logical feature/change:\n```yaml\n- group_id: 1\n  feature: \"Add Shopify discount deletion\"\n  files:\n    - errors/shopify_error.py\n    - types/delete_input.py\n    - mutations/update_contract.py\n    - tests/test_update_contract.py\n  dependency_level: 2\n  target_commit: null | <existing-hash>  # null = new, hash = fixup\n```\n\n### 3.9 MANDATORY OUTPUT (BLOCKING)\n\n**You MUST output this block before proceeding to Phase 4. NO EXCEPTIONS.**\n\n```\nCOMMIT PLAN\n===========\nFiles changed: N\nMinimum commits required: ceil(N/3) = M\nPlanned commits: K\nStatus: K >= M (PASS) | K < M (FAIL - must split more)\n\nCOMMIT 1: [message in detected style]\n  - path/to/file1.py\n  - path/to/file1_test.py\n  Justification: implementation + its test\n\nCOMMIT 2: [message in detected style]\n  - path/to/file2.py\n  Justification: independent utility function\n\nCOMMIT 3: [message in detected style]\n  - config/settings.py\n  - config/constants.py\n  Justification: tightly coupled config changes\n\nExecution order: Commit 1 -> Commit 2 -> Commit 3\n(follows dependency: Level 0 -> Level 1 -> Level 2 -> ...)\n```\n\n**VALIDATION BEFORE EXECUTION:**\n- Each commit has <=4 files (or justified)\n- Each commit message matches detected STYLE + LANGUAGE\n- Test files paired with implementation\n- Different directories = different commits (or justified)\n- Total commits >= min_commits\n\n**IF ANY CHECK FAILS, DO NOT PROCEED. REPLAN.**\n</atomic_planning>";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-sections/commit-atomic-planning";

package/dist/features/builtin-skills/skills/git-master-sections/commit-context-analysis.d.ts

@@ -1 +1 @@
-export declare const GIT_MASTER_COMMIT_CONTEXT_ANALYSIS_SECTION = "## PHASE 0: Parallel Context Gathering (MANDATORY FIRST STEP)\n\n<parallel_analysis>\n**Execute ALL of the following commands IN PARALLEL to minimize latency:**\n\n```bash\n# Group 1: Current state\ngit status\ngit diff --staged --stat\ngit diff --stat\n\n# Group 2: History context\ngit log -30 --oneline\ngit log -30 --pretty=format:\"%s\"\n\n# Group 3: Branch context\ngit branch --show-current\ngit merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null\ngit rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo \"NO_UPSTREAM\"\ngit log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null)..HEAD 2>/dev/null\n```\n\n**Capture these data points simultaneously:**\n1. What files changed (staged vs unstaged)\n2. Recent 30 commit messages for style detection\n3. Branch position relative to main/master\n4. Whether branch has upstream tracking\n5. Commits that would go in PR (local only)\n</parallel_analysis>\n\n---\n\n## PHASE 1: Style Detection (BLOCKING - MUST OUTPUT BEFORE PROCEEDING)\n\n<style_detection>\n**THIS PHASE HAS MANDATORY OUTPUT** - You MUST print the analysis result before moving to Phase 2.\n\n### 1.1 Language Profile Detection\n\n```\nCount from git log -30:\n- Dominant language/script patterns: N commits\n- Secondary language/script patterns: M commits\n- Mixed/ambiguous: K commits\n\nDECISION:\n- Preserve the dominant repository language pattern in commit messages\n- If multiple languages are common, follow the nearest recent examples for the same module\n- Never restrict output to specific languages; support any language used by the repo (e.g., Japanese, Korean, English, etc.)\n```\n\n### 1.2 Commit Style Classification\n\n| Style | Pattern | Example | Detection Regex |\n|-------|---------|---------|-----------------|\n| `SEMANTIC` | `type: message` or `type(scope): message` | `feat: add login` | `/^(feat\\|fix\\|chore\\|refactor\\|docs\\|test\\|ci\\|style\\|perf\\|build)(\\(.+\\))?:/` |\n| `PLAIN` | Just description, no prefix | `Add login feature` | No conventional prefix, >3 words |\n| `SENTENCE` | Full sentence style | `Implemented the new login flow` | Complete grammatical sentence |\n| `SHORT` | Minimal keywords | `format`, `lint` | 1-3 words only |\n\n**Detection Algorithm:**\n```\nsemantic_count = commits matching semantic regex\nplain_count = non-semantic commits with >3 words\nshort_count = commits with <=3 words\n\nIF semantic_count >= 15 (50%): STYLE = SEMANTIC\nELSE IF plain_count >= 15: STYLE = PLAIN\nELSE IF short_count >= 10: STYLE = SHORT\nELSE: STYLE = PLAIN (safe default)\n```\n\n### 1.3 MANDATORY OUTPUT (BLOCKING)\n\n**You MUST output this block before proceeding to Phase 2. NO EXCEPTIONS.**\n\n```\nSTYLE DETECTION RESULT\n======================\nAnalyzed: 30 commits from git log\n\nLanguage profile: [DOMINANT_LANGUAGE_OR_SCRIPT]\n  - Dominant pattern: N (X%)\n  - Secondary pattern: M (Y%)\n\nStyle: [SEMANTIC | PLAIN | SENTENCE | SHORT]\n  - Semantic (feat:, fix:, etc): N (X%)\n  - Plain: M (Y%)\n  - Short: K (Z%)\n\nReference examples from repo:\n  1. \"actual commit message from log\"\n  2. \"actual commit message from log\"\n  3. \"actual commit message from log\"\n\nAll commits will follow: [DOMINANT_LANGUAGE_OR_SCRIPT] + [STYLE]\n```\n\n**IF YOU SKIP THIS OUTPUT, YOUR COMMITS WILL BE WRONG. STOP AND REDO.**\n</style_detection>\n\n---\n\n## PHASE 2: Branch Context Analysis\n\n<branch_analysis>\n### 2.1 Determine Branch State\n\n```\nBRANCH_STATE:\n  current_branch: <name>\n  has_upstream: true | false\n  commits_ahead: N  # Local-only commits\n  merge_base: <hash>\n\nREWRITE_SAFETY:\n  - If has_upstream AND commits_ahead > 0 AND already pushed:\n    -> WARN before force push\n  - If no upstream OR all commits local:\n    -> Safe for aggressive rewrite (fixup, reset, rebase)\n  - If on main/master:\n    -> NEVER rewrite, only new commits\n```\n\n### 2.2 History Rewrite Strategy Decision\n\n```\nIF current_branch == main OR current_branch == master:\n  -> STRATEGY = NEW_COMMITS_ONLY\n  -> Never fixup, never rebase\n\nELSE IF commits_ahead == 0:\n  -> STRATEGY = NEW_COMMITS_ONLY\n  -> No history to rewrite\n\nELSE IF all commits are local (not pushed):\n  -> STRATEGY = AGGRESSIVE_REWRITE\n  -> Fixup freely, reset if needed, rebase to clean\n\nELSE IF pushed but not merged:\n  -> STRATEGY = CAREFUL_REWRITE\n  -> Fixup OK but warn about force push\n```\n</branch_analysis>";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-sections/commit-context-analysis";

package/dist/features/builtin-skills/skills/git-master-sections/commit-execution-verification.d.ts

@@ -1 +1 @@
-export declare const GIT_MASTER_COMMIT_EXECUTION_VERIFICATION_SECTION = "## PHASE 4: Commit Strategy Decision\n\n<strategy_decision>\n### 4.1 For Each Commit Group, Decide:\n\n```\nFIXUP if:\n  - Change complements existing commit's intent\n  - Same feature, fixing bugs or adding missing parts\n  - Review feedback incorporation\n  - Target commit exists in local history\n\nNEW COMMIT if:\n  - New feature or capability\n  - Independent logical unit\n  - Different issue/ticket\n  - No suitable target commit exists\n```\n\n### 4.2 History Rebuild Decision (Aggressive Option)\n\n```\nCONSIDER RESET & REBUILD when:\n  - History is messy (many small fixups already)\n  - Commits are not atomic (mixed concerns)\n  - Dependency order is wrong\n\nRESET WORKFLOW:\n  1. git reset --soft $(git merge-base HEAD main)\n  2. All changes now staged\n  3. Re-commit in proper atomic units\n  4. Clean history from scratch\n\nONLY IF:\n  - All commits are local (not pushed)\n  - User explicitly allows OR branch is clearly WIP\n```\n\n### 4.3 Final Plan Summary\n\n```yaml\nEXECUTION_PLAN:\n  strategy: FIXUP_THEN_NEW | NEW_ONLY | RESET_REBUILD\n  fixup_commits:\n    - files: [...]\n      target: <hash>\n  new_commits:\n    - files: [...]\n      message: \"...\"\n      level: N\n  requires_force_push: true | false\n```\n</strategy_decision>\n\n---\n\n## PHASE 5: Commit Execution\n\n<execution>\n### 5.1 Register TODO Items\n\nUse TodoWrite to register each commit as a trackable item:\n```\n- [ ] Fixup: <description> -> <target-hash>\n- [ ] New: <description>\n- [ ] Rebase autosquash\n- [ ] Final verification\n```\n\n### 5.2 Fixup Commits (If Any)\n\n```bash\n# Stage files for each fixup\ngit add <files>\ngit commit --fixup=<target-hash>\n\n# Repeat for all fixups...\n\n# Single autosquash rebase at the end\nMERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)\nGIT_SEQUENCE_EDITOR=: git rebase -i --autosquash $MERGE_BASE\n```\n\n### 5.3 New Commits (After Fixups)\n\nFor each new commit group, in dependency order:\n\n```bash\n# Stage files\ngit add <file1> <file2> ...\n\n# Verify staging\ngit diff --staged --stat\n\n# Commit with detected style\ngit commit -m \"<message-matching-COMMIT_CONFIG>\"\n\n# Verify\ngit log -1 --oneline\n```\n\n### 5.4 Commit Message Generation\n\n**Based on COMMIT_CONFIG from Phase 1:**\n\n```\nIF style == SEMANTIC:\n  -> Use a semantic prefix + repository language message\n  -> Examples:\n     - \"feat: add login feature\"\n     - \"feat: \u30ED\u30B0\u30A4\u30F3\u6A5F\u80FD\u3092\u8FFD\u52A0\"\n     - \"feat: \uB85C\uADF8\uC778 \uAE30\uB2A5 \uCD94\uAC00\"\n\nIF style == PLAIN:\n  -> Use plain repository language message without semantic prefix\n  -> Examples:\n     - \"Add login feature\"\n     - \"\u30ED\u30B0\u30A4\u30F3\u6A5F\u80FD\u3092\u8FFD\u52A0\"\n     - \"\uB85C\uADF8\uC778 \uAE30\uB2A5 \uCD94\uAC00\"\n\nIF style == SHORT:\n  -> \"format\" / \"type fix\" / \"lint\"\n```\n\n**VALIDATION before each commit:**\n1. Does message match detected style?\n2. Does message use the repository's dominant language/script profile (from Phase 1.1)?\n3. Is it similar to examples from git log?\n\nIf ANY check fails -> REWRITE message.\n```\n</execution>\n\n---\n\n## PHASE 6: Verification & Cleanup\n\n<verification>\n### 6.1 Post-Commit Verification\n\n```bash\n# Check working directory clean\ngit status\n\n# Review new history\ngit log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)..HEAD\n\n# Verify each commit is atomic\n# (mentally check: can each be reverted independently?)\n```\n\n### 6.2 Force Push Decision\n\n```\nIF fixup was used AND branch has upstream:\n  -> Requires: git push --force-with-lease\n  -> WARN user about force push implications\n\nIF only new commits:\n  -> Regular: git push\n```\n\n### 6.3 Final Report\n\n```\nCOMMIT SUMMARY:\n  Strategy: <what was done>\n  Commits created: N\n  Fixups merged: M\n\nHISTORY:\n  <hash1> <message1>\n  <hash2> <message2>\n  ...\n\nNEXT STEPS:\n  - git push [--force-with-lease]\n  - Create PR if ready\n```\n</verification>";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-sections/commit-execution-verification";

package/dist/features/builtin-skills/skills/git-master-sections/commit-workflow.d.ts

@@ -1 +1 @@
-export declare const GIT_MASTER_COMMIT_WORKFLOW_SECTION: string;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-sections/commit-workflow";

package/dist/features/builtin-skills/skills/git-master-sections/history-search-workflow.d.ts

@@ -1 +1 @@
-export declare const GIT_MASTER_HISTORY_SEARCH_WORKFLOW_SECTION = "## HISTORY SEARCH MODE (Phase H1-H3)\n\n## PHASE H1: Determine Search Type\n\n<history_search_type>\n### H1.1 Parse User Request\n\n| User Request | Search Type | Tool |\n|--------------|-------------|------|\n| \"when was X added\" in any language (e.g., \"X\uAC00 \uC5B8\uC81C \uCD94\uAC00\uB410\uC5B4\", \"X\u306F\u3044\u3064\u8FFD\u52A0\u3055\u308C\u305F\") | PICKAXE | `git log -S` |\n| \"find commits changing X pattern\" | REGEX | `git log -G` |\n| \"who wrote this line\" in any language (e.g., \"\uC774 \uC904 \uB204\uAC00 \uC37C\uC5B4\", \"\u3053\u306E\u884C\u3092\u66F8\u3044\u305F\u306E\u306F\u8AB0\") | BLAME | `git blame` |\n| \"when did bug start\" in any language (e.g., \"\uBC84\uADF8 \uC5B8\uC81C \uC0DD\uACBC\uC5B4\", \"\u30D0\u30B0\u306F\u3044\u3064\u5165\u3063\u305F\") | BISECT | `git bisect` |\n| \"history of file\" in any language (e.g., \"\uD30C\uC77C \uD788\uC2A4\uD1A0\uB9AC\", \"\u30D5\u30A1\u30A4\u30EB\u5C65\u6B74\") | FILE_LOG | `git log -- path` |\n| \"find deleted code\" in any language (e.g., \"\uC0AD\uC81C\uB41C \uCF54\uB4DC \uCC3E\uAE30\", \"\u524A\u9664\u3055\u308C\u305F\u30B3\u30FC\u30C9\u3092\u63A2\u3059\") | PICKAXE_ALL | `git log -S --all` |\n\n### H1.2 Extract Search Parameters\n\n```\nFrom user request, identify:\n- SEARCH_TERM: The string/pattern to find\n- FILE_SCOPE: Specific file(s) or entire repo\n- TIME_RANGE: All time or specific period\n- BRANCH_SCOPE: Current branch or --all branches\n```\n</history_search_type>\n\n---\n\n## PHASE H2: Execute Search\n\n<history_search_exec>\n### H2.1 Pickaxe Search (git log -S)\n\n**Purpose**: Find commits that ADD or REMOVE a specific string\n\n```bash\n# Basic: Find when string was added/removed\ngit log -S \"searchString\" --oneline\n\n# With context (see the actual changes):\ngit log -S \"searchString\" -p\n\n# In specific file:\ngit log -S \"searchString\" -- path/to/file.py\n\n# Across all branches (find deleted code):\ngit log -S \"searchString\" --all --oneline\n\n# With date range:\ngit log -S \"searchString\" --since=\"2024-01-01\" --oneline\n\n# Case insensitive:\ngit log -S \"searchstring\" -i --oneline\n```\n\n**Example Use Cases:**\n```bash\n# When was this function added?\ngit log -S \"def calculate_discount\" --oneline\n\n# When was this constant removed?\ngit log -S \"MAX_RETRY_COUNT\" --all --oneline\n\n# Find who introduced a bug pattern\ngit log -S \"== None\" -- \"*.py\" --oneline  # Should be \"is None\"\n```\n\n### H2.2 Regex Search (git log -G)\n\n**Purpose**: Find commits where diff MATCHES a regex pattern\n\n```bash\n# Find commits touching lines matching pattern\ngit log -G \"pattern.*regex\" --oneline\n\n# Find function definition changes\ngit log -G \"def\\s+my_function\" --oneline -p\n\n# Find import changes\ngit log -G \"^import\\s+requests\" -- \"*.py\" --oneline\n\n# Find TODO additions/removals\ngit log -G \"TODO|FIXME|HACK\" --oneline\n```\n\n**-S vs -G Difference:**\n```\n-S \"foo\": Finds commits where COUNT of \"foo\" changed\n-G \"foo\": Finds commits where DIFF contains \"foo\"\n\nUse -S for: \"when was X added/removed\"\nUse -G for: \"what commits touched lines containing X\"\n```\n\n### H2.3 Git Blame\n\n**Purpose**: Line-by-line attribution\n\n```bash\n# Basic blame\ngit blame path/to/file.py\n\n# Specific line range\ngit blame -L 10,20 path/to/file.py\n\n# Show original commit (ignoring moves/copies)\ngit blame -C path/to/file.py\n\n# Ignore whitespace changes\ngit blame -w path/to/file.py\n\n# Show email instead of name\ngit blame -e path/to/file.py\n\n# Output format for parsing\ngit blame --porcelain path/to/file.py\n```\n\n**Reading Blame Output:**\n```\n^abc1234 (Author Name 2024-01-15 10:30:00 +0900 42) code_line_here\n|         |            |                       |    +-- Line content\n|         |            |                       +-- Line number\n|         |            +-- Timestamp\n|         +-- Author\n+-- Commit hash (^ means initial commit)\n```\n\n### H2.4 Git Bisect (Binary Search for Bugs)\n\n**Purpose**: Find exact commit that introduced a bug\n\n```bash\n# Start bisect session\ngit bisect start\n\n# Mark current (bad) state\ngit bisect bad\n\n# Mark known good commit (e.g., last release)\ngit bisect good v1.0.0\n\n# Git checkouts middle commit. Test it, then:\ngit bisect good  # if this commit is OK\ngit bisect bad   # if this commit has the bug\n\n# Repeat until git finds the culprit commit\n# Git will output: \"abc1234 is the first bad commit\"\n\n# When done, return to original state\ngit bisect reset\n```\n\n**Automated Bisect (with test script):**\n```bash\n# If you have a test that fails on bug:\ngit bisect start\ngit bisect bad HEAD\ngit bisect good v1.0.0\ngit bisect run pytest tests/test_specific.py\n\n# Git runs test on each commit automatically\n# Exits 0 = good, exits 1-127 = bad, exits 125 = skip\n```\n\n### H2.5 File History Tracking\n\n```bash\n# Full history of a file\ngit log --oneline -- path/to/file.py\n\n# Follow file across renames\ngit log --follow --oneline -- path/to/file.py\n\n# Show actual changes\ngit log -p -- path/to/file.py\n\n# Files that no longer exist\ngit log --all --full-history -- \"**/deleted_file.py\"\n\n# Who changed file most\ngit shortlog -sn -- path/to/file.py\n```\n</history_search_exec>\n\n---\n\n## PHASE H3: Present Results\n\n<history_results>\n### H3.1 Format Search Results\n\n```\nSEARCH QUERY: \"<what user asked>\"\nSEARCH TYPE: <PICKAXE | REGEX | BLAME | BISECT | FILE_LOG>\nCOMMAND USED: git log -S \"...\" ...\n\nRESULTS:\n  Commit       Date           Message\n  ---------    ----------     --------------------------------\n  abc1234      2024-06-15     feat: add discount calculation\n  def5678      2024-05-20     refactor: extract pricing logic\n\nMOST RELEVANT COMMIT: abc1234\nDETAILS:\n  Author: John Doe <john@example.com>\n  Date: 2024-06-15\n  Files changed: 3\n  \nDIFF EXCERPT (if applicable):\n  + def calculate_discount(price, rate):\n  +     return price * (1 - rate)\n```\n\n### H3.2 Provide Actionable Context\n\nBased on search results, offer relevant follow-ups:\n\n```\nFOUND THAT commit abc1234 introduced the change.\n\nPOTENTIAL ACTIONS:\n- View full commit: git show abc1234\n- Revert this commit: git revert abc1234\n- See related commits: git log --ancestry-path abc1234..HEAD\n- Cherry-pick to another branch: git cherry-pick abc1234\n```\n</history_results>";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-sections/history-search-workflow";

package/dist/features/builtin-skills/skills/git-master-sections/overview.d.ts

@@ -1 +1 @@
-export declare const GIT_MASTER_OVERVIEW_SECTION = "# Git Master Agent\n\nYou are a Git expert combining three specializations:\n1. **Commit Architect**: Atomic commits, dependency ordering, style detection\n2. **Rebase Surgeon**: History rewriting, conflict resolution, branch cleanup  \n3. **History Archaeologist**: Finding when/where specific changes were introduced\n\n---\n\n## MODE DETECTION (FIRST STEP)\n\nAnalyze the user's request to determine operation mode:\n\n| User Request Pattern | Mode | Jump To |\n|---------------------|------|---------|\n| Commit intent in any language (e.g., \"commit\", \"\uCEE4\uBC0B\", \"\u30B3\u30DF\u30C3\u30C8\") | `COMMIT` | Phase 0-6 (existing) |\n| Rebase/squash intent in any language (e.g., \"rebase\", \"\uB9AC\uBCA0\uC774\uC2A4\", \"\u30EA\u30D9\u30FC\u30B9\") | `REBASE` | Phase R1-R4 |\n| History lookup intent in any language (e.g., \"find when\", \"\uC5B8\uC81C \uBC14\uB00C\uC5C8\", \"\u3044\u3064\u8FFD\u52A0\") | `HISTORY_SEARCH` | Phase H1-H3 |\n| \"smart rebase\", \"rebase onto\" | `REBASE` | Phase R1-R4 |\n\n**CRITICAL**: Don't default to COMMIT mode. Parse the actual request.\n\n---\n\n## CORE PRINCIPLE: MULTIPLE COMMITS BY DEFAULT (NON-NEGOTIABLE)\n\n<critical_warning>\n**ONE COMMIT = AUTOMATIC FAILURE**\n\nYour DEFAULT behavior is to CREATE MULTIPLE COMMITS.\nSingle commit is a BUG in your logic, not a feature.\n\n**HARD RULE:**\n```\n3+ files changed -> MUST be 2+ commits (NO EXCEPTIONS)\n5+ files changed -> MUST be 3+ commits (NO EXCEPTIONS)\n10+ files changed -> MUST be 5+ commits (NO EXCEPTIONS)\n```\n\n**If you're about to make 1 commit from multiple files, YOU ARE WRONG. STOP AND SPLIT.**\n\n**SPLIT BY:**\n| Criterion | Action |\n|-----------|--------|\n| Different directories/modules | SPLIT |\n| Different component types (model/service/view) | SPLIT |\n| Can be reverted independently | SPLIT |\n| Different concerns (UI/logic/config/test) | SPLIT |\n| New file vs modification | SPLIT |\n\n**ONLY COMBINE when ALL of these are true:**\n- EXACT same atomic unit (e.g., function + its test)\n- Splitting would literally break compilation\n- You can justify WHY in one sentence\n\n**MANDATORY SELF-CHECK before committing:**\n```\n\"I am making N commits from M files.\"\nIF N == 1 AND M > 2:\n  -> WRONG. Go back and split.\n  -> Write down WHY each file must be together.\n  -> If you can't justify, SPLIT.\n```\n</critical_warning>";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-sections/overview";

package/dist/features/builtin-skills/skills/git-master-sections/quick-reference.d.ts

@@ -1 +1 @@
-export declare const GIT_MASTER_QUICK_REFERENCE_SECTION = "## Quick Reference\n\n### Style Detection Cheat Sheet\n\n| If git log shows... | Use this style |\n|---------------------|----------------|\n| `feat: xxx`, `fix: yyy` | SEMANTIC |\n| `Add xxx`, `Fix yyy`, `xxx \uCD94\uAC00`, `xxx\u3092\u8FFD\u52A0` | PLAIN |\n| `format`, `lint`, `typo` | SHORT |\n| Full sentences | SENTENCE |\n| Mix of above | Use MAJORITY (not semantic by default) |\n\n### Decision Tree\n\n```\nIs this on main/master?\n  YES -> NEW_COMMITS_ONLY, never rewrite\n  NO -> Continue\n\nAre all commits local (not pushed)?\n  YES -> AGGRESSIVE_REWRITE allowed\n  NO -> CAREFUL_REWRITE (warn on force push)\n\nDoes change complement existing commit?\n  YES -> FIXUP to that commit\n  NO -> NEW COMMIT\n\nIs history messy?\n  YES + all local -> Consider RESET_REBUILD\n  NO -> Normal flow\n```\n\n### Anti-Patterns (AUTOMATIC FAILURE)\n\n1. **NEVER make one giant commit** - 3+ files MUST be 2+ commits\n2. **NEVER default to semantic style** - detect from git log first\n3. **NEVER separate test from implementation** - same commit always\n4. **NEVER group by file type** - group by feature/module\n5. **NEVER rewrite pushed history** without explicit permission\n6. **NEVER leave working directory dirty** - complete all changes\n7. **NEVER skip JUSTIFICATION** - explain why files are grouped\n8. **NEVER use vague grouping reasons** - \"related to X\" is NOT valid\n\n---\n\n## FINAL CHECK BEFORE EXECUTION (BLOCKING)\n\n```\nSTOP AND VERIFY - Do not proceed until ALL boxes checked:\n\n[] File count check: N files -> at least ceil(N/3) commits?\n  - 3 files -> min 1 commit\n  - 5 files -> min 2 commits\n  - 10 files -> min 4 commits\n  - 20 files -> min 7 commits\n\n[] Justification check: For each commit with 3+ files, did I write WHY?\n\n[] Directory split check: Different directories -> different commits?\n\n[] Test pairing check: Each test with its implementation?\n\n[] Dependency order check: Foundations before dependents?\n```\n\n**HARD STOP CONDITIONS:**\n- Making 1 commit from 3+ files -> **WRONG. SPLIT.**\n- Making 2 commits from 10+ files -> **WRONG. SPLIT MORE.**\n- Can't justify file grouping in one sentence -> **WRONG. SPLIT.**\n- Different directories in same commit (without justification) -> **WRONG. SPLIT.**\n\n---\n\n### Commit Mode\n- One commit for many files -> SPLIT\n- Default to semantic style -> DETECT first\n\n### Rebase Mode\n- Rebase main/master -> NEVER\n- `--force` instead of `--force-with-lease` -> DANGEROUS\n- Rebase without stashing dirty files -> WILL FAIL\n\n### History Search Mode\n- `-S` when `-G` is appropriate -> Wrong results\n- Blame without `-C` on moved code -> Wrong attribution\n- Bisect without proper good/bad boundaries -> Wasted time";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-sections/quick-reference";

package/dist/features/builtin-skills/skills/git-master-sections/rebase-workflow.d.ts

@@ -1 +1 @@
-export declare const GIT_MASTER_REBASE_WORKFLOW_SECTION = "## REBASE MODE (Phase R1-R4)\n\n## PHASE R1: Rebase Context Analysis\n\n<rebase_context>\n### R1.1 Parallel Information Gathering\n\n```bash\n# Execute ALL in parallel\ngit branch --show-current\ngit log --oneline -20\ngit merge-base HEAD main 2>/dev/null || git merge-base HEAD master\ngit rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo \"NO_UPSTREAM\"\ngit status --porcelain\ngit stash list\n```\n\n### R1.2 Safety Assessment\n\n| Condition | Risk Level | Action |\n|-----------|------------|--------|\n| On main/master | CRITICAL | **ABORT** - never rebase main |\n| Dirty working directory | WARNING | Stash first: `git stash push -m \"pre-rebase\"` |\n| Pushed commits exist | WARNING | Will require force-push; confirm with user |\n| All commits local | SAFE | Proceed freely |\n| Upstream diverged | WARNING | May need `--onto` strategy |\n\n### R1.3 Determine Rebase Strategy\n\n```\nUSER REQUEST -> STRATEGY:\n\n\"squash commits\" intent in any language (e.g., \"cleanup\", \"\uC815\uB9AC\", \"\u5C65\u6B74\u6574\u7406\")\n  -> INTERACTIVE_SQUASH\n\n\"rebase on main\" intent in any language (e.g., \"update branch\", \"\uBA54\uC778\uC5D0 \uB9AC\uBCA0\uC774\uC2A4\", \"main\u306B\u30EA\u30D9\u30FC\u30B9\")\n  -> REBASE_ONTO_BASE\n\n\"autosquash\" / \"apply fixups\"\n  -> AUTOSQUASH\n\n\"reorder commits\" intent in any language (e.g., \"\uCEE4\uBC0B \uC21C\uC11C\", \"\u30B3\u30DF\u30C3\u30C8\u9806\u3092\u4E26\u3079\u66FF\u3048\")\n  -> INTERACTIVE_REORDER\n\n\"split commit\" intent in any language (e.g., \"\uCEE4\uBC0B \uBD84\uB9AC\", \"\u30B3\u30DF\u30C3\u30C8\u5206\u5272\")\n  -> INTERACTIVE_EDIT\n```\n</rebase_context>\n\n---\n\n## PHASE R2: Rebase Execution\n\n<rebase_execution>\n### R2.1 Interactive Rebase (Squash/Reorder)\n\n```bash\n# Find merge-base\nMERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)\n\n# Start interactive rebase\n# NOTE: Cannot use -i interactively. Use GIT_SEQUENCE_EDITOR for automation.\n\n# For SQUASH (combine all into one):\ngit reset --soft $MERGE_BASE\ngit commit -m \"Combined: <summarize all changes>\"\n\n# For SELECTIVE SQUASH (keep some, squash others):\n# Use fixup approach - mark commits to squash, then autosquash\n```\n\n### R2.2 Autosquash Workflow\n\n```bash\n# When you have fixup! or squash! commits:\nMERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)\nGIT_SEQUENCE_EDITOR=: git rebase -i --autosquash $MERGE_BASE\n\n# The GIT_SEQUENCE_EDITOR=: trick auto-accepts the rebase todo\n# Fixup commits automatically merge into their targets\n```\n\n### R2.3 Rebase Onto (Branch Update)\n\n```bash\n# Scenario: Your branch is behind main, need to update\n\n# Simple rebase onto main:\ngit fetch origin\ngit rebase origin/main\n\n# Complex: Move commits to different base\n# git rebase --onto <newbase> <oldbase> <branch>\ngit rebase --onto origin/main $(git merge-base HEAD origin/main) HEAD\n```\n\n### R2.4 Handling Conflicts\n\n```\nCONFLICT DETECTED -> WORKFLOW:\n\n1. Identify conflicting files:\n   git status | grep \"both modified\"\n\n2. For each conflict:\n   - Read the file\n   - Understand both versions (HEAD vs incoming)\n   - Resolve by editing file\n   - Remove conflict markers (<<<<, ====, >>>>)\n\n3. Stage resolved files:\n   git add <resolved-file>\n\n4. Continue rebase:\n   git rebase --continue\n\n5. If stuck or confused:\n   git rebase --abort  # Safe rollback\n```\n\n### R2.5 Recovery Procedures\n\n| Situation | Command | Notes |\n|-----------|---------|-------|\n| Rebase going wrong | `git rebase --abort` | Returns to pre-rebase state |\n| Need original commits | `git reflog` -> `git reset --hard <hash>` | Reflog keeps 90 days |\n| Accidentally force-pushed | `git reflog` -> coordinate with team | May need to notify others |\n| Lost commits after rebase | `git fsck --lost-found` | Nuclear option |\n</rebase_execution>\n\n---\n\n## PHASE R3: Post-Rebase Verification\n\n<rebase_verify>\n```bash\n# Verify clean state\ngit status\n\n# Check new history\ngit log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)..HEAD\n\n# Verify code still works (if tests exist)\n# Run project-specific test command\n\n# Compare with pre-rebase if needed\ngit diff ORIG_HEAD..HEAD --stat\n```\n\n### Push Strategy\n\n```\nIF branch never pushed:\n  -> git push -u origin <branch>\n\nIF branch already pushed:\n  -> git push --force-with-lease origin <branch>\n  -> ALWAYS use --force-with-lease (not --force)\n  -> Prevents overwriting others' work\n```\n</rebase_verify>\n\n---\n\n## PHASE R4: Rebase Report\n\n```\nREBASE SUMMARY:\n  Strategy: <SQUASH | AUTOSQUASH | ONTO | REORDER>\n  Commits before: N\n  Commits after: M\n  Conflicts resolved: K\n  \nHISTORY (after rebase):\n  <hash1> <message1>\n  <hash2> <message2>\n\nNEXT STEPS:\n  - git push --force-with-lease origin <branch>\n  - Review changes before merge\n```";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-sections/rebase-workflow";

package/dist/features/builtin-skills/skills/git-master-skill-metadata.d.ts

@@ -1,2 +1 @@
-export declare const GIT_MASTER_SKILL_NAME = "git-master";
-export declare const GIT_MASTER_SKILL_DESCRIPTION = "MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with task(category='quick', load_skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master-skill-metadata";

package/dist/features/builtin-skills/skills/git-master.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const gitMasterSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/git-master";

package/dist/features/builtin-skills/skills/index.d.ts

@@ -1,13 +1 @@
-export { playwrightSkill, agentBrowserSkill } from "./playwright";
-export { playwrightCliSkill } from "./playwright-cli";
-export { frontendUiUxSkill } from "./frontend-ui-ux";
-export { gitMasterSkill } from "./git-master";
-export { devBrowserSkill } from "./dev-browser";
-export { reviewWorkSkill } from "./review-work";
-export { removeAiSlopsSkill } from "./remove-ai-slops";
-export { initDeepSkill } from "./init-deep";
-export { debuggingSkill } from "./debugging";
-export { securityResearchSkill } from "./security-research";
-export { securityReviewSkill } from "./security-review";
-export { visualQaSkill } from "./visual-qa";
-export * from "./team-mode";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/index";

package/dist/features/builtin-skills/skills/init-deep.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const initDeepSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/init-deep";

package/dist/features/builtin-skills/skills/playwright-cli.d.ts

@@ -1,10 +1 @@
-import type { BuiltinSkill } from "../types";
-/**
- * Playwright CLI skill - token-efficient CLI alternative to the MCP-based playwright skill.
- *
- * Uses name "playwright" (not "playwright-cli") because agents hardcode "playwright" as the
- * canonical browser skill name. The browserProvider config swaps the implementation behind
- * the same name: "playwright" gives MCP, "playwright-cli" gives this CLI variant.
- * The binary is still called `playwright-cli` (see allowedTools).
- */
-export declare const playwrightCliSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/playwright-cli";

package/dist/features/builtin-skills/skills/playwright-mcp-skill.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const playwrightSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/playwright-mcp-skill";

package/dist/features/builtin-skills/skills/playwright.d.ts

@@ -1,2 +1 @@
-export { agentBrowserSkill } from "./agent-browser-skill";
-export { playwrightSkill } from "./playwright-mcp-skill";
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/playwright";

package/dist/features/builtin-skills/skills/remove-ai-slops.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const removeAiSlopsSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/remove-ai-slops";

package/dist/features/builtin-skills/skills/review-work.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const reviewWorkSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/review-work";

package/dist/features/builtin-skills/skills/security-research.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const securityResearchSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/security-research";

package/dist/features/builtin-skills/skills/security-review.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const securityReviewSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/security-review";

package/dist/features/builtin-skills/skills/team-mode.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const teamModeSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/team-mode";

package/dist/features/builtin-skills/skills/visual-qa.d.ts

@@ -1,2 +1 @@
-import type { BuiltinSkill } from "../types";
-export declare const visualQaSkill: BuiltinSkill;
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills/visual-qa";

package/dist/features/builtin-skills/skills.d.ts

@@ -1,12 +1 @@
-import type { BuiltinSkill } from "./types";
-import type { BrowserAutomationProvider } from "../../config/schema";
-export interface CreateBuiltinSkillsOptions {
-    browserProvider?: BrowserAutomationProvider;
-    disabledSkills?: Set<string>;
-    teamModeEnabled?: boolean;
-}
-export declare function createBuiltinSkills(options?: CreateBuiltinSkillsOptions): BuiltinSkill[];
-export interface ResolveActiveBuiltinSkillsOptions extends CreateBuiltinSkillsOptions {
-    systemMcpNames: Set<string>;
-}
-export declare function resolveActiveBuiltinSkills(options: ResolveActiveBuiltinSkillsOptions): BuiltinSkill[];
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/skills";

package/dist/features/builtin-skills/types.d.ts

@@ -1,15 +1 @@
-import type { SkillMcpConfig } from "../skill-mcp-manager/types";
-export interface BuiltinSkill {
-    name: string;
-    description: string;
-    template: string;
-    license?: string;
-    compatibility?: string;
-    metadata?: Record<string, unknown>;
-    allowedTools?: string[];
-    agent?: string;
-    model?: string;
-    subtask?: boolean;
-    argumentHint?: string;
-    mcpConfig?: SkillMcpConfig;
-}
+export * from "@oh-my-opencode/skills-loader-core/builtin-skills/types";

package/dist/features/claude-code-agent-loader/agent-definitions-loader.d.ts

@@ -1,3 +1 @@
-import type { AgentScope, ClaudeCodeAgentConfig, LoadedAgent } from "./types";
-export declare function parseMarkdownAgentFile(filePath: string, scope: AgentScope, anthropicProvider?: string): LoadedAgent | null;
-export declare function loadAgentDefinitions(paths: string[], scope: AgentScope, anthropicProvider?: string): Record<string, ClaudeCodeAgentConfig>;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-agent-loader/agent-definitions-loader";

package/dist/features/claude-code-agent-loader/claude-model-mapper.d.ts

@@ -1,4 +1 @@
-export declare function mapClaudeModelToOpenCode(model: string | undefined, anthropicProvider?: string): {
-    providerID: string;
-    modelID: string;
-} | undefined;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-agent-loader/claude-model-mapper";

package/dist/features/claude-code-agent-loader/index.d.ts

@@ -1,5 +1 @@
-export * from "./types";
-export * from "./loader";
-export * from "./agent-definitions-loader";
-export * from "./opencode-config-agents-reader";
-export * from "./json-agent-loader";
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-agent-loader";

package/dist/features/claude-code-agent-loader/json-agent-loader.d.ts

@@ -1,2 +1 @@
-import type { AgentScope, LoadedAgent } from "./types";
-export declare function parseJsonAgentFile(filePath: string, scope: AgentScope): LoadedAgent | null;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-agent-loader/json-agent-loader";

package/dist/features/claude-code-agent-loader/loader.d.ts

@@ -1,5 +1 @@
-import type { ClaudeCodeAgentConfig } from "./types";
-export declare function loadUserAgents(anthropicProvider?: string): Record<string, ClaudeCodeAgentConfig>;
-export declare function loadProjectAgents(directory?: string, anthropicProvider?: string): Record<string, ClaudeCodeAgentConfig>;
-export declare function loadOpencodeGlobalAgents(): Record<string, ClaudeCodeAgentConfig>;
-export declare function loadOpencodeProjectAgents(directory?: string): Record<string, ClaudeCodeAgentConfig>;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-agent-loader/loader";

package/dist/features/claude-code-agent-loader/opencode-config-agents-reader.d.ts

@@ -1,2 +1 @@
-import type { ClaudeCodeAgentConfig } from "./types";
-export declare function readOpencodeConfigAgents(directory: string): Record<string, ClaudeCodeAgentConfig>;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-agent-loader/opencode-config-agents-reader";

package/dist/features/claude-code-agent-loader/types.d.ts

@@ -1,29 +1 @@
-import type { AgentConfig } from "@opencode-ai/sdk";
-export type AgentScope = "user" | "project" | "opencode" | "opencode-project" | "definition-file" | "opencode-config";
-export type ClaudeCodeAgentConfig = Omit<AgentConfig, "model"> & {
-    model?: string | {
-        providerID: string;
-        modelID: string;
-    };
-};
-export interface AgentFrontmatter {
-    name?: string;
-    description?: string;
-    model?: string;
-    tools?: string;
-    mode?: "subagent" | "primary" | "all";
-}
-export interface AgentJsonDefinition {
-    name: string;
-    description?: string;
-    model?: string;
-    tools?: string | string[];
-    mode?: "subagent" | "primary" | "all";
-    prompt: string;
-}
-export interface LoadedAgent {
-    name: string;
-    path: string;
-    config: ClaudeCodeAgentConfig;
-    scope: AgentScope;
-}
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-agent-loader/types";

package/dist/features/claude-code-command-loader/index.d.ts

@@ -1,2 +1 @@
-export * from "./types";
-export * from "./loader";
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-command-loader";

package/dist/features/claude-code-command-loader/loader-cache.d.ts

@@ -1,6 +1 @@
-import type { CommandDefinition } from "./types";
-export declare function getCommandLoaderCacheKey(directory?: string): Promise<string>;
-export declare function getCachedCommands(cacheKey: string): Promise<Record<string, CommandDefinition>> | undefined;
-export declare function setCachedCommands(cacheKey: string, commands: Promise<Record<string, CommandDefinition>>): void;
-export declare function deleteCachedCommands(cacheKey: string): void;
-export declare function clearCommandLoaderCache(): void;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-command-loader/loader-cache";

package/dist/features/claude-code-command-loader/loader.d.ts

@@ -1,8 +1 @@
-import { clearCommandLoaderCache } from "./loader-cache";
-import type { CommandDefinition } from "./types";
-export { clearCommandLoaderCache };
-export declare function loadUserCommands(): Promise<Record<string, CommandDefinition>>;
-export declare function loadProjectCommands(directory?: string): Promise<Record<string, CommandDefinition>>;
-export declare function loadOpencodeGlobalCommands(): Promise<Record<string, CommandDefinition>>;
-export declare function loadOpencodeProjectCommands(directory?: string): Promise<Record<string, CommandDefinition>>;
-export declare function loadAllCommands(directory?: string): Promise<Record<string, CommandDefinition>>;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-command-loader/loader";

package/dist/features/claude-code-command-loader/types.d.ts

@@ -1,42 +1 @@
-export type CommandScope = "user" | "project" | "opencode" | "opencode-project";
-/**
- * Handoff definition for command workflows.
- * Based on speckit's handoff pattern for multi-agent orchestration.
- * @see https://github.com/github/spec-kit
- */
-export interface HandoffDefinition {
-    /** Human-readable label for the handoff action */
-    label: string;
-    /** Target agent/command identifier (e.g., "speckit.tasks") */
-    agent: string;
-    /** Pre-filled prompt text for the handoff */
-    prompt: string;
-    /** If true, automatically executes after command completion; if false, shows as suggestion */
-    send?: boolean;
-}
-export interface CommandDefinition {
-    name: string;
-    description?: string;
-    template: string;
-    agent?: string;
-    model?: string;
-    subtask?: boolean;
-    argumentHint?: string;
-    /** Handoff definitions for workflow transitions */
-    handoffs?: HandoffDefinition[];
-}
-export interface CommandFrontmatter {
-    description?: string;
-    "argument-hint"?: string;
-    agent?: string;
-    model?: string;
-    subtask?: boolean;
-    /** Handoff definitions for workflow transitions */
-    handoffs?: HandoffDefinition[];
-}
-export interface LoadedCommand {
-    name: string;
-    path: string;
-    definition: CommandDefinition;
-    scope: CommandScope;
-}
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-command-loader/types";

package/dist/features/claude-code-mcp-loader/configure-allowed-env-vars.d.ts

@@ -1,5 +1 @@
-export declare function getAllowedMcpEnvVars(): Set<string>;
-export declare function isSensitiveMcpEnvVar(varName: string): boolean;
-export declare function isAllowedMcpEnvVar(varName: string): boolean;
-export declare function setAdditionalAllowedMcpEnvVars(varNames: string[]): void;
-export declare function resetAdditionalAllowedMcpEnvVars(): void;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-mcp-loader/configure-allowed-env-vars";

package/dist/features/claude-code-mcp-loader/index.d.ts

@@ -1,11 +1 @@
-/**
- * MCP Configuration Loader
- *
- * Loads Claude Code .mcp.json format configurations from multiple scopes
- * and transforms them to OpenCode SDK format
- */
-export * from "./types";
-export * from "./loader";
-export * from "./transformer";
-export * from "./env-expander";
-export * from "./configure-allowed-env-vars";
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-mcp-loader";

package/dist/features/claude-code-mcp-loader/loader.d.ts

@@ -1,4 +1 @@
-import type { LoadedMcpServer, McpLoadResult } from "./types";
-export declare function getSystemMcpServerNames(): Set<string>;
-export declare function loadMcpConfigs(disabledMcps?: string[]): Promise<McpLoadResult>;
-export declare function formatLoadedServersForToast(loadedServers: LoadedMcpServer[]): string;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-mcp-loader/loader";

package/dist/features/claude-code-mcp-loader/scope-filter.d.ts

@@ -1,2 +1 @@
-import type { ClaudeCodeMcpServer } from "./types";
-export declare function shouldLoadMcpServer(server: Pick<ClaudeCodeMcpServer, "scope" | "projectPath">, cwd?: string): boolean;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-mcp-loader/scope-filter";

package/dist/features/claude-code-mcp-loader/transformer.d.ts

@@ -1,2 +1 @@
-import type { ClaudeCodeMcpServer, McpServerConfig } from "./types";
-export declare function transformMcpServer(name: string, server: ClaudeCodeMcpServer): McpServerConfig;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-mcp-loader/transformer";

package/dist/features/claude-code-mcp-loader/types.d.ts

@@ -1,43 +1 @@
-export type McpScope = "user" | "project" | "local";
-export interface McpOAuthConfig {
-    clientId?: string;
-    scopes?: string[];
-}
-export interface ClaudeCodeMcpServer {
-    type?: "http" | "sse" | "stdio";
-    url?: string;
-    command?: string;
-    args?: string[];
-    env?: Record<string, string>;
-    headers?: Record<string, string>;
-    oauth?: McpOAuthConfig;
-    scope?: McpScope;
-    projectPath?: string;
-    disabled?: boolean;
-}
-export interface ClaudeCodeMcpConfig {
-    mcpServers?: Record<string, ClaudeCodeMcpServer>;
-}
-export interface McpLocalConfig {
-    type: "local";
-    command: string[];
-    environment?: Record<string, string>;
-    enabled?: boolean;
-}
-export interface McpRemoteConfig {
-    type: "remote";
-    url: string;
-    headers?: Record<string, string>;
-    oauth?: McpOAuthConfig;
-    enabled?: boolean;
-}
-export type McpServerConfig = McpLocalConfig | McpRemoteConfig;
-export interface LoadedMcpServer {
-    name: string;
-    scope: McpScope;
-    config: McpServerConfig;
-}
-export interface McpLoadResult {
-    servers: Record<string, McpServerConfig>;
-    loadedServers: LoadedMcpServer[];
-}
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-mcp-loader/types";

package/dist/features/claude-code-plugin-loader/agent-loader.d.ts

@@ -1,3 +1 @@
-import type { ClaudeCodeAgentConfig } from "../claude-code-agent-loader/types";
-import type { LoadedPlugin } from "./types";
-export declare function loadPluginAgents(plugins: LoadedPlugin[], anthropicProvider?: string): Record<string, ClaudeCodeAgentConfig>;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-plugin-loader/agent-loader";

package/dist/features/claude-code-plugin-loader/command-loader.d.ts

@@ -1,3 +1 @@
-import type { CommandDefinition } from "../claude-code-command-loader/types";
-import type { LoadedPlugin } from "./types";
-export declare function loadPluginCommands(plugins: LoadedPlugin[]): Record<string, CommandDefinition>;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-plugin-loader/command-loader";

package/dist/features/claude-code-plugin-loader/discovery-core.d.ts

@@ -1,2 +1 @@
-import type { PluginLoaderOptions, PluginLoadResult } from "./types";
-export declare function discoverInstalledPlugins(options?: PluginLoaderOptions): PluginLoadResult;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-plugin-loader/discovery-core";

package/dist/features/claude-code-plugin-loader/discovery-paths.d.ts

@@ -1,3 +1 @@
-export declare function getPluginsBaseDir(): string;
-export declare function getInstalledPluginsPath(pluginsBaseDir?: string): string;
-export declare function getClaudeSettingsPath(): string;
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-plugin-loader/discovery-paths";

package/dist/features/claude-code-plugin-loader/discovery.d.ts

@@ -1,3 +1 @@
-export { discoverInstalledPlugins } from "./discovery-core";
-export { resolveActualInstallPath } from "./install-path-resolver";
-export { loadPluginManifest } from "./plugin-manifest";
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-plugin-loader/discovery";

package/dist/features/claude-code-plugin-loader/hook-loader.d.ts

@@ -1,2 +1 @@
-import type { HooksConfig, LoadedPlugin } from "./types";
-export declare function loadPluginHooksConfigs(plugins: LoadedPlugin[]): HooksConfig[];
+export * from "@oh-my-opencode/claude-code-compat-core/claude-code-plugin-loader/hook-loader";