@hiai-gg/hiai-opencode 0.1.1 → 0.1.2

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

@@ -1,229 +1,229 @@
-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>`
+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 +1,64 @@
-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>`
+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>`