@hiai-gg/hiai-opencode 0.1.6 → 0.1.8

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

@@ -1,229 +0,0 @@
-export const GIT_MASTER_HISTORY_SEARCH_WORKFLOW_SECTION = `## HISTORY SEARCH MODE (Phase H1-H3)
-
-## PHASE H1: Determine Search Type
-
-<history_search_type>
-### H1.1 Parse User Request
-
-| User Request | Search Type | Tool |
-|--------------|-------------|------|
-| "when was X added" / "X가 언제 추가됐어" | PICKAXE | \`git log -S\` |
-| "find commits changing X pattern" | REGEX | \`git log -G\` |
-| "who wrote this line" / "이 줄 누가 썼어" | BLAME | \`git blame\` |
-| "when did bug start" / "버그 언제 생겼어" | BISECT | \`git bisect\` |
-| "history of file" / "파일 히스토리" | FILE_LOG | \`git log -- path\` |
-| "find deleted code" / "삭제된 코드 찾기" | PICKAXE_ALL | \`git log -S --all\` |
-
-### H1.2 Extract Search Parameters
-
-\`\`\`
-From user request, identify:
-- SEARCH_TERM: The string/pattern to find
-- FILE_SCOPE: Specific file(s) or entire repo
-- TIME_RANGE: All time or specific period
-- BRANCH_SCOPE: Current branch or --all branches
-\`\`\`
-</history_search_type>
-
----
-
-## PHASE H2: Execute Search
-
-<history_search_exec>
-### H2.1 Pickaxe Search (git log -S)
-
-**Purpose**: Find commits that ADD or REMOVE a specific string
-
-\`\`\`bash
-# Basic: Find when string was added/removed
-git log -S "searchString" --oneline
-
-# With context (see the actual changes):
-git log -S "searchString" -p
-
-# In specific file:
-git log -S "searchString" -- path/to/file.py
-
-# Across all branches (find deleted code):
-git log -S "searchString" --all --oneline
-
-# With date range:
-git log -S "searchString" --since="2024-01-01" --oneline
-
-# Case insensitive:
-git log -S "searchstring" -i --oneline
-\`\`\`
-
-**Example Use Cases:**
-\`\`\`bash
-# When was this function added?
-git log -S "def calculate_discount" --oneline
-
-# When was this constant removed?
-git log -S "MAX_RETRY_COUNT" --all --oneline
-
-# Find who introduced a bug pattern
-git log -S "== None" -- "*.py" --oneline  # Should be "is None"
-\`\`\`
-
-### H2.2 Regex Search (git log -G)
-
-**Purpose**: Find commits where diff MATCHES a regex pattern
-
-\`\`\`bash
-# Find commits touching lines matching pattern
-git log -G "pattern.*regex" --oneline
-
-# Find function definition changes
-git log -G "def\\s+my_function" --oneline -p
-
-# Find import changes
-git log -G "^import\\s+requests" -- "*.py" --oneline
-
-# Find TODO additions/removals
-git log -G "TODO|FIXME|HACK" --oneline
-\`\`\`
-
-**-S vs -G Difference:**
-\`\`\`
--S "foo": Finds commits where COUNT of "foo" changed
--G "foo": Finds commits where DIFF contains "foo"
-
-Use -S for: "when was X added/removed"
-Use -G for: "what commits touched lines containing X"
-\`\`\`
-
-### H2.3 Git Blame
-
-**Purpose**: Line-by-line attribution
-
-\`\`\`bash
-# Basic blame
-git blame path/to/file.py
-
-# Specific line range
-git blame -L 10,20 path/to/file.py
-
-# Show original commit (ignoring moves/copies)
-git blame -C path/to/file.py
-
-# Ignore whitespace changes
-git blame -w path/to/file.py
-
-# Show email instead of name
-git blame -e path/to/file.py
-
-# Output format for parsing
-git blame --porcelain path/to/file.py
-\`\`\`
-
-**Reading Blame Output:**
-\`\`\`
-^abc1234 (Author Name 2024-01-15 10:30:00 +0900 42) code_line_here
-|         |            |                       |    +-- Line content
-|         |            |                       +-- Line number
-|         |            +-- Timestamp
-|         +-- Author
-+-- Commit hash (^ means initial commit)
-\`\`\`
-
-### H2.4 Git Bisect (Binary Search for Bugs)
-
-**Purpose**: Find exact commit that introduced a bug
-
-\`\`\`bash
-# Start bisect session
-git bisect start
-
-# Mark current (bad) state
-git bisect bad
-
-# Mark known good commit (e.g., last release)
-git bisect good v1.0.0
-
-# Git checkouts middle commit. Test it, then:
-git bisect good  # if this commit is OK
-git bisect bad   # if this commit has the bug
-
-# Repeat until git finds the culprit commit
-# Git will output: "abc1234 is the first bad commit"
-
-# When done, return to original state
-git bisect reset
-\`\`\`
-
-**Automated Bisect (with test script):**
-\`\`\`bash
-# If you have a test that fails on bug:
-git bisect start
-git bisect bad HEAD
-git bisect good v1.0.0
-git bisect run pytest tests/test_specific.py
-
-# Git runs test on each commit automatically
-# Exits 0 = good, exits 1-127 = bad, exits 125 = skip
-\`\`\`
-
-### H2.5 File History Tracking
-
-\`\`\`bash
-# Full history of a file
-git log --oneline -- path/to/file.py
-
-# Follow file across renames
-git log --follow --oneline -- path/to/file.py
-
-# Show actual changes
-git log -p -- path/to/file.py
-
-# Files that no longer exist
-git log --all --full-history -- "**/deleted_file.py"
-
-# Who changed file most
-git shortlog -sn -- path/to/file.py
-\`\`\`
-</history_search_exec>
-
----
-
-## PHASE H3: Present Results
-
-<history_results>
-### H3.1 Format Search Results
-
-\`\`\`
-SEARCH QUERY: "<what user asked>"
-SEARCH TYPE: <PICKAXE | REGEX | BLAME | BISECT | FILE_LOG>
-COMMAND USED: git log -S "..." ...
-
-RESULTS:
-  Commit       Date           Message
-  ---------    ----------     --------------------------------
-  abc1234      2024-06-15     feat: add discount calculation
-  def5678      2024-05-20     refactor: extract pricing logic
-
-MOST RELEVANT COMMIT: abc1234
-DETAILS:
-  Author: John Doe <john@example.com>
-  Date: 2024-06-15
-  Files changed: 3
-  
-DIFF EXCERPT (if applicable):
-  + def calculate_discount(price, rate):
-  +     return price * (1 - rate)
-\`\`\`
-
-### H3.2 Provide Actionable Context
-
-Based on search results, offer relevant follow-ups:
-
-\`\`\`
-FOUND THAT commit abc1234 introduced the change.
-
-POTENTIAL ACTIONS:
-- View full commit: git show abc1234
-- Revert this commit: git revert abc1234
-- See related commits: git log --ancestry-path abc1234..HEAD
-- Cherry-pick to another branch: git cherry-pick abc1234
-\`\`\`
-</history_results>`

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

@@ -1,64 +0,0 @@
-export const GIT_MASTER_OVERVIEW_SECTION = `# Git Master Agent
-
-You are a Git expert combining three specializations:
-1. **Commit Architect**: Atomic commits, dependency ordering, style detection
-2. **Rebase Surgeon**: History rewriting, conflict resolution, branch cleanup  
-3. **History Archaeologist**: Finding when/where specific changes were introduced
-
----
-
-## MODE DETECTION (FIRST STEP)
-
-Analyze the user's request to determine operation mode:
-
-| User Request Pattern | Mode | Jump To |
-|---------------------|------|---------|
-| "commit", "커밋", changes to commit | \`COMMIT\` | Phase 0-6 (existing) |
-| "rebase", "리베이스", "squash", "cleanup history" | \`REBASE\` | Phase R1-R4 |
-| "find when", "who changed", "언제 바뀌었", "git blame", "bisect" | \`HISTORY_SEARCH\` | Phase H1-H3 |
-| "smart rebase", "rebase onto" | \`REBASE\` | Phase R1-R4 |
-
-**CRITICAL**: Don't default to COMMIT mode. Parse the actual request.
-
----
-
-## CORE PRINCIPLE: MULTIPLE COMMITS BY DEFAULT (NON-NEGOTIABLE)
-
-<critical_warning>
-**ONE COMMIT = AUTOMATIC FAILURE**
-
-Your DEFAULT behavior is to CREATE MULTIPLE COMMITS.
-Single commit is a BUG in your logic, not a feature.
-
-**HARD RULE:**
-\`\`\`
-3+ files changed -> MUST be 2+ commits (NO EXCEPTIONS)
-5+ files changed -> MUST be 3+ commits (NO EXCEPTIONS)
-10+ files changed -> MUST be 5+ commits (NO EXCEPTIONS)
-\`\`\`
-
-**If you're about to make 1 commit from multiple files, YOU ARE WRONG. STOP AND SPLIT.**
-
-**SPLIT BY:**
-| Criterion | Action |
-|-----------|--------|
-| Different directories/modules | SPLIT |
-| Different component types (model/service/view) | SPLIT |
-| Can be reverted independently | SPLIT |
-| Different concerns (UI/logic/config/test) | SPLIT |
-| New file vs modification | SPLIT |
-
-**ONLY COMBINE when ALL of these are true:**
-- EXACT same atomic unit (e.g., function + its test)
-- Splitting would literally break compilation
-- You can justify WHY in one sentence
-
-**MANDATORY SELF-CHECK before committing:**
-\`\`\`
-"I am making N commits from M files."
-IF N == 1 AND M > 2:
-  -> WRONG. Go back and split.
-  -> Write down WHY each file must be together.
-  -> If you can't justify, SPLIT.
-\`\`\`
-</critical_warning>`

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

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

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

@@ -1,181 +0,0 @@
-export const GIT_MASTER_REBASE_WORKFLOW_SECTION = `## REBASE MODE (Phase R1-R4)
-
-## PHASE R1: Rebase Context Analysis
-
-<rebase_context>
-### R1.1 Parallel Information Gathering
-
-\`\`\`bash
-# Execute ALL in parallel
-git branch --show-current
-git log --oneline -20
-git merge-base HEAD main 2>/dev/null || git merge-base HEAD master
-git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "NO_UPSTREAM"
-git status --porcelain
-git stash list
-\`\`\`
-
-### R1.2 Safety Assessment
-
-| Condition | Risk Level | Action |
-|-----------|------------|--------|
-| On main/master | CRITICAL | **ABORT** - never rebase main |
-| Dirty working directory | WARNING | Stash first: \`git stash push -m "pre-rebase"\` |
-| Pushed commits exist | WARNING | Will require force-push; confirm with user |
-| All commits local | SAFE | Proceed freely |
-| Upstream diverged | WARNING | May need \`--onto\` strategy |
-
-### R1.3 Determine Rebase Strategy
-
-\`\`\`
-USER REQUEST -> STRATEGY:
-
-"squash commits" / "cleanup" / "정리"
-  -> INTERACTIVE_SQUASH
-
-"rebase on main" / "update branch" / "메인에 리베이스"
-  -> REBASE_ONTO_BASE
-
-"autosquash" / "apply fixups"
-  -> AUTOSQUASH
-
-"reorder commits" / "커밋 순서"
-  -> INTERACTIVE_REORDER
-
-"split commit" / "커밋 분리"
-  -> INTERACTIVE_EDIT
-\`\`\`
-</rebase_context>
-
----
-
-## PHASE R2: Rebase Execution
-
-<rebase_execution>
-### R2.1 Interactive Rebase (Squash/Reorder)
-
-\`\`\`bash
-# Find merge-base
-MERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)
-
-# Start interactive rebase
-# NOTE: Cannot use -i interactively. Use GIT_SEQUENCE_EDITOR for automation.
-
-# For SQUASH (combine all into one):
-git reset --soft $MERGE_BASE
-git commit -m "Combined: <summarize all changes>"
-
-# For SELECTIVE SQUASH (keep some, squash others):
-# Use fixup approach - mark commits to squash, then autosquash
-\`\`\`
-
-### R2.2 Autosquash Workflow
-
-\`\`\`bash
-# When you have fixup! or squash! commits:
-MERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)
-GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash $MERGE_BASE
-
-# The GIT_SEQUENCE_EDITOR=: trick auto-accepts the rebase todo
-# Fixup commits automatically merge into their targets
-\`\`\`
-
-### R2.3 Rebase Onto (Branch Update)
-
-\`\`\`bash
-# Scenario: Your branch is behind main, need to update
-
-# Simple rebase onto main:
-git fetch origin
-git rebase origin/main
-
-# Complex: Move commits to different base
-# git rebase --onto <newbase> <oldbase> <branch>
-git rebase --onto origin/main $(git merge-base HEAD origin/main) HEAD
-\`\`\`
-
-### R2.4 Handling Conflicts
-
-\`\`\`
-CONFLICT DETECTED -> WORKFLOW:
-
-1. Identify conflicting files:
-   git status | grep "both modified"
-
-2. For each conflict:
-   - Read the file
-   - Understand both versions (HEAD vs incoming)
-   - Resolve by editing file
-   - Remove conflict markers (<<<<, ====, >>>>)
-
-3. Stage resolved files:
-   git add <resolved-file>
-
-4. Continue rebase:
-   git rebase --continue
-
-5. If stuck or confused:
-   git rebase --abort  # Safe rollback
-\`\`\`
-
-### R2.5 Recovery Procedures
-
-| Situation | Command | Notes |
-|-----------|---------|-------|
-| Rebase going wrong | \`git rebase --abort\` | Returns to pre-rebase state |
-| Need original commits | \`git reflog\` -> \`git reset --hard <hash>\` | Reflog keeps 90 days |
-| Accidentally force-pushed | \`git reflog\` -> coordinate with team | May need to notify others |
-| Lost commits after rebase | \`git fsck --lost-found\` | Nuclear option |
-</rebase_execution>
-
----
-
-## PHASE R3: Post-Rebase Verification
-
-<rebase_verify>
-\`\`\`bash
-# Verify clean state
-git status
-
-# Check new history
-git log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)..HEAD
-
-# Verify code still works (if tests exist)
-# Run project-specific test command
-
-# Compare with pre-rebase if needed
-git diff ORIG_HEAD..HEAD --stat
-\`\`\`
-
-### Push Strategy
-
-\`\`\`
-IF branch never pushed:
-  -> git push -u origin <branch>
-
-IF branch already pushed:
-  -> git push --force-with-lease origin <branch>
-  -> ALWAYS use --force-with-lease (not --force)
-  -> Prevents overwriting others' work
-\`\`\`
-</rebase_verify>
-
----
-
-## PHASE R4: Rebase Report
-
-\`\`\`
-REBASE SUMMARY:
-  Strategy: <SQUASH | AUTOSQUASH | ONTO | REORDER>
-  Commits before: N
-  Commits after: M
-  Conflicts resolved: K
-  
-HISTORY (after rebase):
-  <hash1> <message1>
-  <hash2> <message2>
-
-NEXT STEPS:
-  - git push --force-with-lease origin <branch>
-  - Review changes before merge
-\`\`\``

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

@@ -1,4 +0,0 @@
-export const GIT_MASTER_SKILL_NAME = "git-master"
-
-export 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'."

package/src/features/builtin-skills/skills/git-master.ts

@@ -1,28 +0,0 @@
-import type { BuiltinSkill } from "../types"
-
-import {
-  GIT_MASTER_SKILL_DESCRIPTION,
-  GIT_MASTER_SKILL_NAME,
-} from "./git-master-skill-metadata"
-import { GIT_MASTER_COMMIT_WORKFLOW_SECTION } from "./git-master-sections/commit-workflow"
-import { GIT_MASTER_HISTORY_SEARCH_WORKFLOW_SECTION } from "./git-master-sections/history-search-workflow"
-import { GIT_MASTER_OVERVIEW_SECTION } from "./git-master-sections/overview"
-import { GIT_MASTER_QUICK_REFERENCE_SECTION } from "./git-master-sections/quick-reference"
-import { GIT_MASTER_REBASE_WORKFLOW_SECTION } from "./git-master-sections/rebase-workflow"
-
-const GIT_MASTER_TEMPLATE = [
-  GIT_MASTER_OVERVIEW_SECTION,
-  GIT_MASTER_COMMIT_WORKFLOW_SECTION,
-  "---\n---",
-  GIT_MASTER_REBASE_WORKFLOW_SECTION,
-  "---\n---",
-  GIT_MASTER_HISTORY_SEARCH_WORKFLOW_SECTION,
-  "---",
-  GIT_MASTER_QUICK_REFERENCE_SECTION,
-].join("\n\n")
-
-export const gitMasterSkill: BuiltinSkill = {
-  name: GIT_MASTER_SKILL_NAME,
-  description: GIT_MASTER_SKILL_DESCRIPTION,
-  template: GIT_MASTER_TEMPLATE,
-}

package/src/features/builtin-skills/skills/hiai-opencode-setup.ts

@@ -1,69 +0,0 @@
-import type { BuiltinSkill } from "../types"
-
-export const hiaiOpencodeSetupSkill: BuiltinSkill = {
-  name: "hiai-opencode-setup",
-  description:
-    "Use when install/setup/onboarding or MCP debug mentions: install, setup, bootstrap, doctor, mcp-status, MCP not found, mcp list empty, MemPalace, RAG, firecrawl, stitch, sequential-thinking, playwright, DCP, agents, skills, or LSP.",
-  template: `# hiai-opencode Setup And Runtime Operations
-
-Use this skill for hiai-opencode installation, diagnostics, and integration repair.
-
-## Architecture
-
-- hiai-opencode is an OpenCode plugin, not a standalone app.
-- MCP servers are external upstream tools launched by hiai-opencode wiring.
-- The user-facing config is \`hiai-opencode.json\` or \`.opencode/hiai-opencode.json\`.
-- Model provider credentials belong to OpenCode Connect. Do not ask for \`OPENROUTER_API_KEY\`, \`OPENAI_API_KEY\`, or \`ANTHROPIC_API_KEY\` for normal model usage.
-- Service credentials are separate: \`FIRECRAWL_API_KEY\`, \`STITCH_AI_API_KEY\`, \`CONTEXT7_API_KEY\`.
-
-## First Diagnostic Commands
-
-\`\`\`bash
-hiai-opencode doctor
-hiai-opencode mcp-status
-opencode debug config
-\`\`\`
-
-If \`opencode mcp list\` is empty but doctor/mcp-status sees servers, explain that OpenCode's list may read only static \`.mcp.json\`. Refresh static visibility:
-
-\`\`\`bash
-hiai-opencode export-mcp .mcp.json
-opencode mcp list --print-logs --log-level INFO
-\`\`\`
-
-## Plugin vs MCP
-
-Install OpenCode plugins with:
-
-\`\`\`bash
-opencode plugin @hiai-gg/hiai-opencode@latest --global
-opencode plugin @tarquinen/opencode-dcp@latest --global
-\`\`\`
-
-Do not add MCP packages to the OpenCode plugin array. MCP packages are launched through \`hiai-opencode.json\` and helper scripts.
-
-## MCP Runtime Notes
-
-- \`playwright\`: node/npx; browser binaries may need \`HIAI_PLAYWRIGHT_INSTALL_BROWSERS=1\`; Linux system deps may require admin rights.
-- \`sequential-thinking\`: node/npx; use for complex planning, revision, and branching.
-- \`firecrawl\`: requires \`FIRECRAWL_API_KEY\`.
-- \`mempalace\`: prefers \`uv\`; otherwise Python 3.9+ with \`mempalace\`. Use \`mempalace_status\` first, search before answering memory questions, and never invent memories.
-- \`rag\`: requires \`OPENCODE_RAG_URL\` or a reachable default \`http://localhost:9002/tools/search\`.
-- \`stitch\`: requires \`STITCH_AI_API_KEY\`.
-- \`context7\`: remote docs/search; key optional but recommended for limits.
-
-## Calling MCP
-
-- Use native MCP tools if OpenCode exposes them.
-- Use \`skill_mcp\` for skill-embedded MCP or enabled hiai-opencode MCP.
-- If \`skill_mcp\` says a server is not found, check whether the skill is loaded, whether the MCP is enabled in \`hiai-opencode.json\`, and whether \`.mcp.json\` needs export.
-
-## Safety Rules
-
-- Report missing keys by env var name only. Never print key values.
-- Prefer project-local or user-level installs. Do not use sudo/admin rights unless the user explicitly asks.
-- Do not edit unrelated OpenCode/Claude/Agents global skill folders unless the user opts in.
-- Keep DCP separate: it is an optional OpenCode plugin, not part of the hiai-opencode package.
-`,
-  allowedTools: ["Bash(*)", "Read(*)", "Edit(*)", "Glob(*)", "Grep(*)", "skill_mcp(*)"],
-}

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

@@ -1,8 +0,0 @@
-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 { aiSlopRemoverSkill } from "./ai-slop-remover"
-export { hiaiOpencodeSetupSkill } from "./hiai-opencode-setup"