super-opencode 1.1.0 → 1.1.2

package/.opencode/commands/soc-cleanup.md

@@ -1,107 +1,107 @@
----
-description: "Systematically clean up code, remove dead code, and optimize project structure"
----
-
-# /soc-cleanup
-
-## 1. Command Overview
-The `/soc-cleanup` command is the "Janitor" of the codebase. It safely identifies and removes technical debt, unused exports, and dead code. It operates in two modes: `Safe` (conservative) and `Aggressive` (deep cleaning). Its primary directive is "Do No Harm."
-
-## 2. Triggers & Routing
-The command routes cleanup tasks based on the `--type` flag.
-
-| Trigger Scenario | Flag | Target Agent | Tool Used |
-| :--- | :--- | :--- | :--- |
-| **Dead Code** | `--type code` | `[quality]` | TSPrune, Knip |
-| **Unused Imports** | `--type imports` | `[quality]` | ESLint/Birome |
-| **File Structure** | `--type files` | `[architect]` | Filesystem Analysis |
-| **Deep Clean** | `--type all` | `[quality]` | All tools |
-
-## 3. Usage & Arguments
-```bash
-/soc-cleanup [target] [flags]
-```
-
-### Arguments
--   **`[target]`**: Directory or file to clean (default: current context).
-
-### Flags
--   **`--type [code|imports|files|all]`**: **MANDATORY**.
--   **`--safe`**: (Default) Only removes code with 0 references.
--   **`--aggressive`**: Removes code with indirect/suspect references (requires confirmation).
--   **`--preview`**: Lists changes without applying them (Dry Run).
-
-## 4. Behavioral Flow (Orchestration)
-
-### Phase 1: Analysis (The Scanner)
-1.  **Map**: Scans `[target]` for exports and imports.
-2.  **Trace**: Builds a dependency graph.
-3.  **Flag**: Identifies "orphan" nodes (code with no incoming edges).
-
-### Phase 2: Plan (The Stratagem)
--   If `safe`: Select only orphans with 0 references.
--   If `aggressive`: Select orphans + "soft" references (comments, test-only usage).
-
-### Phase 3: Execution (The Broom)
-1.  **Backup**: (Implicit) Relies on Git.
-2.  **Remove**: Deletes lines/files.
-3.  **Verify**: Runs build/tests. If fail -> Revert.
-
-## 5. Output Guidelines (The Contract)
-
-### Cleanup Report
-```markdown
-## Cleanup Report: [Target]
-
-### Summary
--   **Removed**: 15 unused exports
--   **Deleted**: 2 dead files
--   **Bytes Saved**: 4.5KB
-
-### Actions Taken
--   [x] Removed `oldFunction` from `src/utils.ts` (0 refs).
--   [x] Deleted `src/components/unused-modal.tsx`.
-
-### Skipped (Safety Check)
--   [ ] `legacyAuth.ts` (Referenced in TODO comment).
-```
-
-## 6. Examples
-
-### A. Safe Import Cleanup
-```bash
-/soc-cleanup src/ --type imports --safe
-```
-*Effect:* Removes unused `import` statements and sorts remaining ones.
-
-### B. Dead Code Preview
-```bash
-/soc-cleanup --type code --preview
-```
-*Effect:* Lists all exported functions that are never imported, but does not delete them.
-
-## 7. Dependencies & Capabilities
-
-### Agents
--   **Quality**: `@[.opencode/agents/quality.md]` - Primary agent for code analysis.
--   **Architect**: `@[.opencode/agents/architect.md]` - For structural cleanup.
-
-### Skills
--   **Safety Check**: `@[.opencode/skills/security-audit/SKILL.md]` - ensuring cleanup doesn't remove security gates.
--   **Reflexion**: `@[.opencode/skills/reflexion/SKILL.md]` - Recovering if cleanup breaks the build.
-
-### MCP Integration
--   **`context7`**: Verifying if "unused" code is actually a framework entry point (e.g., Next.js pages).
--   **`filesystem`**: Moving and deleting files.
-
-## 8. Boundaries
-
-**Will:**
--   Remove unused imports.
--   Delete files with 0 references (in `aggressive` mode).
--   Consolidate duplicate logic (if explicitly identified).
-
-**Will Not:**
--   **Delete "Commented Out" Code**: Unless explicitly told to.
--   **Touch Config Files**: (e.g., `tsconfig.json`) without explicit intent.
--   **Break Public APIs**: Will not remove exports from `index.ts` files in libraries.
+---
+description: "Systematically clean up code, remove dead code, and optimize project structure"
+---
+
+# /soc-cleanup
+
+## 1. Command Overview
+The `/soc-cleanup` command is the "Janitor" of the codebase. It safely identifies and removes technical debt, unused exports, and dead code. It operates in two modes: `Safe` (conservative) and `Aggressive` (deep cleaning). Its primary directive is "Do No Harm."
+
+## 2. Triggers & Routing
+The command routes cleanup tasks based on the `--type` flag.
+
+| Trigger Scenario | Flag | Target Agent | Tool Used |
+| :--- | :--- | :--- | :--- |
+| **Dead Code** | `--type code` | `[quality]` | TSPrune, Knip |
+| **Unused Imports** | `--type imports` | `[quality]` | ESLint/Birome |
+| **File Structure** | `--type files` | `[architect]` | Filesystem Analysis |
+| **Deep Clean** | `--type all` | `[quality]` | All tools |
+
+## 3. Usage & Arguments
+```bash
+/soc-cleanup [target] [flags]
+```
+
+### Arguments
+-   **`[target]`**: Directory or file to clean (default: current context).
+
+### Flags
+-   **`--type [code|imports|files|all]`**: **MANDATORY**.
+-   **`--safe`**: (Default) Only removes code with 0 references.
+-   **`--aggressive`**: Removes code with indirect/suspect references (requires confirmation).
+-   **`--preview`**: Lists changes without applying them (Dry Run).
+
+## 4. Behavioral Flow (Orchestration)
+
+### Phase 1: Analysis (The Scanner)
+1.  **Map**: Scans `[target]` for exports and imports.
+2.  **Trace**: Builds a dependency graph.
+3.  **Flag**: Identifies "orphan" nodes (code with no incoming edges).
+
+### Phase 2: Plan (The Stratagem)
+-   If `safe`: Select only orphans with 0 references.
+-   If `aggressive`: Select orphans + "soft" references (comments, test-only usage).
+
+### Phase 3: Execution (The Broom)
+1.  **Backup**: (Implicit) Relies on Git.
+2.  **Remove**: Deletes lines/files.
+3.  **Verify**: Runs build/tests. If fail -> Revert.
+
+## 5. Output Guidelines (The Contract)
+
+### Cleanup Report
+```markdown
+## Cleanup Report: [Target]
+
+### Summary
+-   **Removed**: 15 unused exports
+-   **Deleted**: 2 dead files
+-   **Bytes Saved**: 4.5KB
+
+### Actions Taken
+-   [x] Removed `oldFunction` from `src/utils.ts` (0 refs).
+-   [x] Deleted `src/components/unused-modal.tsx`.
+
+### Skipped (Safety Check)
+-   [ ] `legacyAuth.ts` (Referenced in TODO comment).
+```
+
+## 6. Examples
+
+### A. Safe Import Cleanup
+```bash
+/soc-cleanup src/ --type imports --safe
+```
+*Effect:* Removes unused `import` statements and sorts remaining ones.
+
+### B. Dead Code Preview
+```bash
+/soc-cleanup --type code --preview
+```
+*Effect:* Lists all exported functions that are never imported, but does not delete them.
+
+## 7. Dependencies & Capabilities
+
+### Agents
+-   **Quality**: `@[.opencode/agents/quality.md]` - Primary agent for code analysis.
+-   **Architect**: `@[.opencode/agents/architect.md]` - For structural cleanup.
+
+### Skills
+-   **Safety Check**: `@[.opencode/skills/security-audit/SKILL.md]` - ensuring cleanup doesn't remove security gates.
+-   **Reflexion**: `@[.opencode/skills/reflexion/SKILL.md]` - Recovering if cleanup breaks the build.
+
+### MCP Integration
+-   **`context7`**: Verifying if "unused" code is actually a framework entry point (e.g., Next.js pages).
+-   **`filesystem`**: Moving and deleting files.
+
+## 8. Boundaries
+
+**Will:**
+-   Remove unused imports.
+-   Delete files with 0 references (in `aggressive` mode).
+-   Consolidate duplicate logic (if explicitly identified).
+
+**Will Not:**
+-   **Delete "Commented Out" Code**: Unless explicitly told to.
+-   **Touch Config Files**: (e.g., `tsconfig.json`) without explicit intent.
+-   **Break Public APIs**: Will not remove exports from `index.ts` files in libraries.

package/.opencode/commands/soc-design.md

@@ -1,5 +1,4 @@
 ---
-name: design
 description: "Design system architecture, APIs, and component interfaces with comprehensive specifications"
 ---
 

package/.opencode/commands/soc-explain.md

@@ -1,113 +1,113 @@
----
-description: Code explanation and understanding
----
-
-# /soc-explain
-
-## 1. Command Overview
-The `/soc-explain` command is the "Tutor." It translates complex code, errors, or concepts into natural language. It adapts its depth to the user's needs, from simple analogies to expert technical deep-dives. It generates documentation that can be saved.
-
-## 2. Triggers & Routing
-The command uses the `writer` agent effectively to synthesize information.
-
-| Trigger Scenario | Flag | Target Agent | Style |
-| :--- | :--- | :--- | :--- |
-| **High Level** | `--depth simple` | `[writer]` | Analogies, non-technical |
-| **Standard** | `--depth detailed` | `[writer]` | Code logic, flow, syntax |
-| **Deep Dive** | `--depth expert` | `[architect]` | Memory, performance, edge cases |
-
-## 3. Usage & Arguments
-```bash
-/soc-explain [target] [flags]
-```
-
-### Arguments
--   **`[target]`**: Code snippet, file path, error message, or concept (e.g., "Dependency Injection").
-
-### Flags
--   **`--depth [simple|detailed|expert]`**: (Default: `detailed`).
--   **`--context [file]`**: Add extra context for better explanation.
-
-## 4. Behavioral Flow (Orchestration)
-
-### Phase 1: Analysis
-1.  **Parse**: Is the target a file, a string, or a concept?
-2.  **Context**: If it's an error, where did it come from? If it's code, what language?
-
-### Phase 2: Synthesis (The Lesson)
--   **Analogy**: "Think of a Promise like a pizza buzzer..."
--   **Technical**: "It wraps the value in a microtask queue..."
--   **Example**: "Here is how you use it:"
-
-### Phase 3: Formatting
--   Structure with clear Headers.
--   Use Code Blocks for syntax.
--   Highlight "Key Takeaways."
-
-## 5. Output Guidelines (The Contract)
-
-### Explanation Document
-```markdown
-## Explanation: [Topic]
-
-### Summary
-[1-2 sentences. The TL;DR.]
-
-### Conceptual Analogy (If Simple)
-[Mundane comparison]
-
-### Technical Breakdown
--   **Component A**: Does X.
--   **Component B**: Does Y.
-
-### Code Example
-```javascript
-// Before
-badCode()
-
-// After (corrected/explained)
-goodCode()
-```
-
-### Key Takeaways
-1.  [Point 1]
-2.  [Point 2]
-```
-
-## 6. Examples
-
-### A. Async/Await (Expert)
-```bash
-/soc-explain "How Node Event Loop works" --depth expert
-```
-*Effect:* Explains Phases (Timers, Poll, Check), Microtasks vs Macrotasks, and `process.nextTick`.
-
-### B. Error Parsing
-```bash
-/soc-explain "TypeError: Cannot read property 'map' of undefined"
-```
-*Effect:* Explains that the array is missing, helps identify the source variable, suggests Optional Chaining (`?.`).
-
-## 7. Dependencies & Capabilities
-
-### Agents
--   **Writer**: `@[.opencode/agents/writer.md]` - Primary explainer.
--   **Architect**: `@[.opencode/agents/architect.md]` - For system-level concepts.
-
-### Skills
--   **Simplification**: `@[.opencode/skills/simplification/SKILL.md]` - To de-jargonize complex topics.
-
-### MCP Integration
--   **`context7`**: Fetching official docs to cite sources.
--   **`read_file`**: Reading the full content of the file being explained.
-
-## 8. Boundaries
-
-**Will:**
--   Explain *why* code works.
--   Suggest *best practices*.
--   Debug *logic* errors via explanation.
-
-**Will Not:**
--   **Write the Fix**: It explains the fix; `/soc-implement` writes it.
--   **Execute Code**: It analyzes static text.
+---
+description: Code explanation and understanding
+---
+
+# /soc-explain
+
+## 1. Command Overview
+The `/soc-explain` command is the "Tutor." It translates complex code, errors, or concepts into natural language. It adapts its depth to the user's needs, from simple analogies to expert technical deep-dives. It generates documentation that can be saved.
+
+## 2. Triggers & Routing
+The command uses the `writer` agent effectively to synthesize information.
+
+| Trigger Scenario | Flag | Target Agent | Style |
+| :--- | :--- | :--- | :--- |
+| **High Level** | `--depth simple` | `[writer]` | Analogies, non-technical |
+| **Standard** | `--depth detailed` | `[writer]` | Code logic, flow, syntax |
+| **Deep Dive** | `--depth expert` | `[architect]` | Memory, performance, edge cases |
+
+## 3. Usage & Arguments
+```bash
+/soc-explain [target] [flags]
+```
+
+### Arguments
+-   **`[target]`**: Code snippet, file path, error message, or concept (e.g., "Dependency Injection").
+
+### Flags
+-   **`--depth [simple|detailed|expert]`**: (Default: `detailed`).
+-   **`--context [file]`**: Add extra context for better explanation.
+
+## 4. Behavioral Flow (Orchestration)
+
+### Phase 1: Analysis
+1.  **Parse**: Is the target a file, a string, or a concept?
+2.  **Context**: If it's an error, where did it come from? If it's code, what language?
+
+### Phase 2: Synthesis (The Lesson)
+-   **Analogy**: "Think of a Promise like a pizza buzzer..."
+-   **Technical**: "It wraps the value in a microtask queue..."
+-   **Example**: "Here is how you use it:"
+
+### Phase 3: Formatting
+-   Structure with clear Headers.
+-   Use Code Blocks for syntax.
+-   Highlight "Key Takeaways."
+
+## 5. Output Guidelines (The Contract)
+
+### Explanation Document
+```markdown
+## Explanation: [Topic]
+
+### Summary
+[1-2 sentences. The TL;DR.]
+
+### Conceptual Analogy (If Simple)
+[Mundane comparison]
+
+### Technical Breakdown
+-   **Component A**: Does X.
+-   **Component B**: Does Y.
+
+### Code Example
+```javascript
+// Before
+badCode()
+
+// After (corrected/explained)
+goodCode()
+```
+
+### Key Takeaways
+1.  [Point 1]
+2.  [Point 2]
+```
+
+## 6. Examples
+
+### A. Async/Await (Expert)
+```bash
+/soc-explain "How Node Event Loop works" --depth expert
+```
+*Effect:* Explains Phases (Timers, Poll, Check), Microtasks vs Macrotasks, and `process.nextTick`.
+
+### B. Error Parsing
+```bash
+/soc-explain "TypeError: Cannot read property 'map' of undefined"
+```
+*Effect:* Explains that the array is missing, helps identify the source variable, suggests Optional Chaining (`?.`).
+
+## 7. Dependencies & Capabilities
+
+### Agents
+-   **Writer**: `@[.opencode/agents/writer.md]` - Primary explainer.
+-   **Architect**: `@[.opencode/agents/architect.md]` - For system-level concepts.
+
+### Skills
+-   **Simplification**: `@[.opencode/skills/simplification/SKILL.md]` - To de-jargonize complex topics.
+
+### MCP Integration
+-   **`context7`**: Fetching official docs to cite sources.
+-   **`read_file`**: Reading the full content of the file being explained.
+
+## 8. Boundaries
+
+**Will:**
+-   Explain *why* code works.
+-   Suggest *best practices*.
+-   Debug *logic* errors via explanation.
+
+**Will Not:**
+-   **Write the Fix**: It explains the fix; `/soc-implement` writes it.
+-   **Execute Code**: It analyzes static text.

package/.opencode/commands/soc-git.md

@@ -1,104 +1,104 @@
----
-description: "Git operations with intelligent commit messages and workflow optimization"
----
-
-# /soc-git
-
-## 1. Command Overview
-The `/soc-git` command is the "Version Controller." It wraps standard git operations with intelligence. It can analyze diffs to generate Conventional Commit messages, check for accidental secrets before pushing, and manage branching strategies.
-
-## 2. Triggers & Routing
-The command routes to the `writer` agent for message generation and `security` for pre-push checks.
-
-| Trigger Scenario | Flag | Target Agent | Action |
-| :--- | :--- | :--- | :--- |
-| **Commit Message** | `--smart` | `[writer]` | Generate `feat(scope): desc` |
-| **Pre-Push** | `push` | `[security]` | Scan for secrets |
-| **Branching** | `branch` | `[pm-agent]` | Enforce naming conventions |
-
-## 3. Usage & Arguments
-```bash
-/soc-git [operation] [args] [flags]
-```
-
-### Arguments
--   **`[operation]`**: `commit`, `push`, `pull`, `branch`, `status`, `diff`.
-
-### Flags
--   **`--smart`**: Auto-generate messages/descriptions.
--   **`--force`**: Bypass safety checks (Use with caution).
-
-## 4. Behavioral Flow (Orchestration)
-
-### Phase 1: Context Analysis
-1.  **Status Check**: Run `git status`.
-2.  **Diff Analysis**: Run `git diff --staged`.
-3.  **Safety Check**: Scan pending changes for keys/env files.
-
-### Phase 2: Operations
--   **Commit**:
-    -   If `--smart`: Feed diff to LLM -> Generate Conventional Commit.
-    -   If standard: Execute `git commit -m`.
--   **Push**:
-    -   Check upstream. If missing, auto-set `-u origin`.
--   **Branch**:
-    -   Normalize name (e.g., `My Feature` -> `feat/my-feature`).
-
-### Phase 3: Post-Op
--   Confirm success.
--   Show Next Step (e.g., "Ready to open PR").
-
-## 5. Output Guidelines (The Contract)
-
-### Git Operation Result
-```markdown
-## Git: [Operation]
-
-### Status
-✅ Success / ❌ Failure
-
-### Details
--   **Branch**: `feat/user-auth`
--   **Commit**: `a1b2c3d` - "feat(auth): add login route"
-
-### Tips
--   [ ] Run `/test` before pushing.
-```
-
-## 6. Examples
-
-### A. Smart Commit
-```bash
-/soc-git commit --smart
-```
-*Effect:* Analyzes staged files, detects added login logic, commits with: `feat(auth): implement user login flow`.
-
-### B. Branch Creation
-```bash
-/soc-git branch "Update README"
-```
-*Effect:* Creates and checks out `docs/update-readme` (auto-categorized).
-
-## 7. Dependencies & Capabilities
-
-### Agents
--   **Writer**: `@[.opencode/agents/writer.md]` - For commit messages.
--   **Security**: `@[.opencode/agents/security.md]` - For pre-commit hooks.
-
-### Skills
--   **Security Audit**: `@[.opencode/skills/security-audit/SKILL.md]` - Scanning staged files.
-
-### MCP Integration
--   **`run_command`**: Executing actual git binaries.
--   **`filesystem`**: Reading ignores and config.
-
-## 8. Boundaries
-
-**Will:**
--   Execute git commands.
--   Generate text for messages.
--   Block commits with secrets (unless `--force`).
-
-**Will Not:**
--   **Solve Merge Conflicts**: It will report them, but user must resolve.
--   **Rewrite History**: No `rebase` or `reset --hard` without explicit user confirmation.
+---
+description: "Git operations with intelligent commit messages and workflow optimization"
+---
+
+# /soc-git
+
+## 1. Command Overview
+The `/soc-git` command is the "Version Controller." It wraps standard git operations with intelligence. It can analyze diffs to generate Conventional Commit messages, check for accidental secrets before pushing, and manage branching strategies.
+
+## 2. Triggers & Routing
+The command routes to the `writer` agent for message generation and `security` for pre-push checks.
+
+| Trigger Scenario | Flag | Target Agent | Action |
+| :--- | :--- | :--- | :--- |
+| **Commit Message** | `--smart` | `[writer]` | Generate `feat(scope): desc` |
+| **Pre-Push** | `push` | `[security]` | Scan for secrets |
+| **Branching** | `branch` | `[pm-agent]` | Enforce naming conventions |
+
+## 3. Usage & Arguments
+```bash
+/soc-git [operation] [args] [flags]
+```
+
+### Arguments
+-   **`[operation]`**: `commit`, `push`, `pull`, `branch`, `status`, `diff`.
+
+### Flags
+-   **`--smart`**: Auto-generate messages/descriptions.
+-   **`--force`**: Bypass safety checks (Use with caution).
+
+## 4. Behavioral Flow (Orchestration)
+
+### Phase 1: Context Analysis
+1.  **Status Check**: Run `git status`.
+2.  **Diff Analysis**: Run `git diff --staged`.
+3.  **Safety Check**: Scan pending changes for keys/env files.
+
+### Phase 2: Operations
+-   **Commit**:
+    -   If `--smart`: Feed diff to LLM -> Generate Conventional Commit.
+    -   If standard: Execute `git commit -m`.
+-   **Push**:
+    -   Check upstream. If missing, auto-set `-u origin`.
+-   **Branch**:
+    -   Normalize name (e.g., `My Feature` -> `feat/my-feature`).
+
+### Phase 3: Post-Op
+-   Confirm success.
+-   Show Next Step (e.g., "Ready to open PR").
+
+## 5. Output Guidelines (The Contract)
+
+### Git Operation Result
+```markdown
+## Git: [Operation]
+
+### Status
+✅ Success / ❌ Failure
+
+### Details
+-   **Branch**: `feat/user-auth`
+-   **Commit**: `a1b2c3d` - "feat(auth): add login route"
+
+### Tips
+-   [ ] Run `/test` before pushing.
+```
+
+## 6. Examples
+
+### A. Smart Commit
+```bash
+/soc-git commit --smart
+```
+*Effect:* Analyzes staged files, detects added login logic, commits with: `feat(auth): implement user login flow`.
+
+### B. Branch Creation
+```bash
+/soc-git branch "Update README"
+```
+*Effect:* Creates and checks out `docs/update-readme` (auto-categorized).
+
+## 7. Dependencies & Capabilities
+
+### Agents
+-   **Writer**: `@[.opencode/agents/writer.md]` - For commit messages.
+-   **Security**: `@[.opencode/agents/security.md]` - For pre-commit hooks.
+
+### Skills
+-   **Security Audit**: `@[.opencode/skills/security-audit/SKILL.md]` - Scanning staged files.
+
+### MCP Integration
+-   **`run_command`**: Executing actual git binaries.
+-   **`filesystem`**: Reading ignores and config.
+
+## 8. Boundaries
+
+**Will:**
+-   Execute git commands.
+-   Generate text for messages.
+-   Block commits with secrets (unless `--force`).
+
+**Will Not:**
+-   **Solve Merge Conflicts**: It will report them, but user must resolve.
+-   **Rewrite History**: No `rebase` or `reset --hard` without explicit user confirmation.