super-opencode 1.1.2 → 1.2.0

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

@@ -5,9 +5,11 @@ 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 |
@@ -17,36 +19,43 @@ The command uses the `writer` agent effectively to synthesize information.
 | **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").
+
+- **`[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.
+
+- **`--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?
+
+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:"
+
+- **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."
+
+- Structure with clear Headers.
+- Use Code Blocks for syntax.
+- Highlight "Key Takeaways."
 
 ## 5. Output Guidelines (The Contract)
 
 ### Explanation Document
+
 ```markdown
 ## Explanation: [Topic]
 
@@ -70,8 +79,10 @@ goodCode()
 ```
 
 ### Key Takeaways
-1.  [Point 1]
-2.  [Point 2]
+
+1. [Point 1]
+2. [Point 2]
+
 ```
 
 ## 6. Examples
@@ -80,34 +91,46 @@ goodCode()
 ```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.
+
+- **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.
+
+- **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.
+
+- **`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.
+
+- 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.
+
+- **Write the Fix**: It explains the fix; `/soc-implement` writes it.
+- **Execute Code**: It analyzes static text.
+
+## User Instruction
+
+The user have executed the `/soc-explain` command by parsing the user's arguments provided in `<user-instruction>$ARGUMENTS</user-instruction>`, then analyze the specified target (code snippet, file path, error message, or concept) to determine its type and context, route to the appropriate agent based on depth level—writer agent for simple analogies and detailed explanations, or architect agent for expert-level system concepts—adapt the explanation style to match the requested depth (simple with analogies, detailed with code logic, or expert with performance and edge cases), incorporate additional context files if provided via `--context`, and generate a structured explanation document with summary, technical breakdown, code examples, and key takeaways.

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

@@ -5,9 +5,11 @@ description: "Git operations with intelligent commit messages and workflow optim
 # /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 |
@@ -17,40 +19,47 @@ The command routes to the `writer` agent for message generation and `security` f
 | **Branching** | `branch` | `[pm-agent]` | Enforce naming conventions |
 
 ## 3. Usage & Arguments
+
 ```bash
 /soc-git [operation] [args] [flags]
 ```
 
 ### Arguments
--   **`[operation]`**: `commit`, `push`, `pull`, `branch`, `status`, `diff`.
+
+- **`[operation]`**: `commit`, `push`, `pull`, `branch`, `status`, `diff`.
 
 ### Flags
--   **`--smart`**: Auto-generate messages/descriptions.
--   **`--force`**: Bypass safety checks (Use with caution).
+
+- **`--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.
+
+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`).
+
+- **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").
+
+- Confirm success.
+- Show Next Step (e.g., "Ready to open PR").
 
 ## 5. Output Guidelines (The Contract)
 
 ### Git Operation Result
+
 ```markdown
 ## Git: [Operation]
 
@@ -68,37 +77,50 @@ The command routes to the `writer` agent for message generation and `security` f
 ## 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.
+
+- **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.
+
+- **Security Audit**: `@[.opencode/skills/security-audit/SKILL.md]` - Scanning staged files.
 
 ### MCP Integration
--   **`run_command`**: Executing actual git binaries.
--   **`filesystem`**: Reading ignores and config.
+
+- **`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`).
+
+- 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.
+
+- **Solve Merge Conflicts**: It will report them, but user must resolve.
+- **Rewrite History**: No `rebase` or `reset --hard` without explicit user confirmation.
+
+## User Instruction
+
+The user have executed the `/soc-git` command by parsing the user's arguments provided in `<user-instruction>$ARGUMENTS</user-instruction>`, then perform the specified git operation (commit, push, pull, branch, status, or diff) with the provided arguments, route to the appropriate agent for intelligent assistance—using the writer agent to generate conventional commit messages when `--smart` is specified, or the security agent to scan for secrets before push operations—analyze the current repository context through git status and diff analysis, apply safety checks to prevent accidental commits of secrets or sensitive files, normalize branch names to follow conventions when creating new branches, and provide clear operation results with next-step recommendations.

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

@@ -5,9 +5,11 @@ description: Help and command reference
 # /soc-help
 
 ## 1. Command Overview
+
 The `/soc-help` command is the "Librarian." It serves as the primary documentation interface for the agent system. It explains *how* to use the other commands, details what each agent does, and lists available skills. It uses the `researcher` agent to find answers within the system's own documentation.
 
 ## 2. Triggers & Routing
+
 The command is self-contained but may use `researcher` for deep queries.
 
 | Trigger Scenario | Flag | Target Agent | Action |
@@ -17,29 +19,35 @@ The command is self-contained but may use `researcher` for deep queries.
 | **Workflow Guide** | `[topic]` | `[researcher]` | Summarize best practices |
 
 ## 3. Usage & Arguments
+
 ```bash
 /soc-help [target] [flags]
 ```
 
 ### Arguments
--   **`[target]`**: (Optional) Specific command (`implement`), agent (`backend`), or topic (`workflows`). Default: Shows index.
+
+- **`[target]`**: (Optional) Specific command (`implement`), agent (`backend`), or topic (`workflows`). Default: Shows index.
 
 ### Flags
--   **`--verbose`**: Show detailed descriptions and hidden flags.
+
+- **`--verbose`**: Show detailed descriptions and hidden flags.
 
 ## 4. Behavioral Flow (Orchestration)
 
 ### Phase 1: Lookup
-1.  **Index**: Check if target is a known Command, Agent, or Skill.
-2.  **Search**: If unknown, grep `.opencode/` documentation for keywords.
+
+1. **Index**: Check if target is a known Command, Agent, or Skill.
+2. **Search**: If unknown, grep `.opencode/` documentation for keywords.
 
 ### Phase 2: Formatting
--   **Structure**: Group by Category (Workflow vs Skill).
--   **Clarity**: Show "Quick Start" snippets.
+
+- **Structure**: Group by Category (Workflow vs Skill).
+- **Clarity**: Show "Quick Start" snippets.
 
 ## 5. Output Guidelines (The Contract)
 
 ### Help Document
+
 ```markdown
 ## Help: [Target]
 
@@ -60,35 +68,48 @@ The command is self-contained but may use `researcher` for deep queries.
 ## 6. Examples
 
 ### A. Command Help
+
 ```bash
 /soc-help implement
 ```
+
 *Effect:* Displays usage for `/soc-implement`, including flags like `--agent` and `--test`.
 
 ### B. Agent Role
+
 ```bash
 /soc-help backend
 ```
+
 *Effect:* Shows the `backend` agent's persona, including "Prime Directives" and "Restrictions."
 
 ## 7. Dependencies & Capabilities
 
 ### Agents
--   **Researcher**: `@[.opencode/agents/researcher.md]` - For finding unstructured help.
+
+- **Researcher**: `@[.opencode/agents/researcher.md]` - For finding unstructured help.
 
 ### Skills
--   **None**: This is a read-only command.
+
+- **None**: This is a read-only command.
 
 ### MCP Integration
--   **`filesystem`**: Reading documentation files.
+
+- **`filesystem`**: Reading documentation files.
 
 ## 8. Boundaries
 
 **Will:**
--   Explain system capabilities.
--   List available tools.
--   Provide syntax examples.
+
+- Explain system capabilities.
+- List available tools.
+- Provide syntax examples.
 
 **Will Not:**
--   **Execute Commands**: It only explains them.
--   **Hallucinate Features**: Only lists what exists in `.opencode/`.
+
+- **Execute Commands**: It only explains them.
+- **Hallucinate Features**: Only lists what exists in `.opencode/`.
+
+## User Instruction
+
+The user have executed the `/soc-help` command by parsing the user's arguments provided in `<user-instruction>$ARGUMENTS</user-instruction>`, then look up the specified target (command, agent, skill, or topic) in the system documentation, search the `.opencode/` directory for relevant information if the target is unknown, and format a comprehensive help document showing the description, usage syntax, key features, and related commands for the requested item, providing quick start snippets and grouping information by category for clarity.

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

@@ -5,53 +5,65 @@ description: Code implementation with best practices
 # /soc-implement
 
 ## 1. Command Overview
+
 The `/soc-implement` command is the execution engine of the agent system. It transforms approved designs and specifications into production-ready code. It enforces strict quality control, testing (TDD), and "self-correction" loops via the `reflexion` skill. It does not plan; it executes.
 
 ## 2. Triggers & Routing
+
 The command routes to specialized sub-agents based on the `--agent` flag or file context.
 
 | Trigger Scenario | Flag | Target Agent | Context Injected |
 | :--- | :--- | :--- | :--- |
 | **API/Database Logic** | `--agent backend` | `[backend]` | DB Schemas, Error Handling Middleware |
 | **UI/Components** | `--agent frontend` | `[frontend]` | Design System, A11y Rules, Hooks |
+| **Mobile Apps** | `--agent mobile` | `[mobile-agent]` | React Native, Flutter, Platform APIs |
+| **Data Pipelines** | `--agent data` | `[data-agent]` | ETL, Analytics, Data Warehouse |
+| **Infrastructure** | `--agent devops` | `[devops-agent]` | CI/CD, Deployment, IaC |
 | **Testing/QA** | `--agent quality` | `[quality]` | Test Runner Config, Coverage Reports |
 | **Refactoring** | `--agent fullstack` | `[backend]` + `[frontend]` | Cross-layer dependencies |
 
 ## 3. Usage & Arguments
+
 ```bash
 /soc-implement [target] [flags]
 ```
 
 ### Arguments
--   **`[target]`**: The feature or file to implement (e.g., "Login Flow", "src/components/Button.tsx").
+
+- **`[target]`**: The feature or file to implement (e.g., "Login Flow", "src/components/Button.tsx").
 
 ### Flags
--   **`--agent [backend|frontend|quality]`**: **MANDATORY**. Specifies the executing persona.
--   **`--test`**: (Default: true) Run capabilities tests after implementation.
--   **`--document`**: (Default: true) Update associated documentation/comments.
+
+- **`--agent [backend|frontend|quality]`**: **MANDATORY**. Specifies the executing persona.
+- **`--test`**: (Default: true) Run capabilities tests after implementation.
+- **`--document`**: (Default: true) Update associated documentation/comments.
 
 ## 4. Behavioral Flow (Orchestration)
 
 ### Phase 1: Pre-Flight (Confidence Check)
-1.  **Read**: Review existing code and referencing `design.md` or `requirements`.
-2.  **Verify**: Check for patterns (e.g., "How do existing controllers handle errors?").
-3.  **Gate**: If confidence < 80%, ask user/PM for clarification.
+
+1. **Read**: Review existing code and referencing `design.md` or `requirements`.
+2. **Verify**: Check for patterns (e.g., "How do existing controllers handle errors?").
+3. **Gate**: If confidence < 80%, ask user/PM for clarification.
 
 ### Phase 2: Execution (The Loop)
-1.  **Test**: Write the test case first (TDD) if applicable.
-2.  **Edit**: Apply changes using `replace_file_content` or `write_to_file`.
-3.  **Verify**: Run the project's build/test command.
-    *   *If Fail*: Trigger `reflexion` skill (Why did it fail? -> Fix -> Retry).
-    *   *Limit*: Max 3 retries before asking for help.
+
+1. **Test**: Write the test case first (TDD) if applicable.
+2. **Edit**: Apply changes using `replace_file_content` or `write_to_file`.
+3. **Verify**: Run the project's build/test command.
+    - *If Fail*: Trigger `reflexion` skill (Why did it fail? -> Fix -> Retry).
+    - *Limit*: Max 3 retries before asking for help.
 
 ### Phase 3: Post-Flight (Self Check)
--   Did I leave any `console.log`?
--   Are inputs sanitized?
--   Did I break the build?
+
+- Did I leave any `console.log`?
+- Are inputs sanitized?
+- Did I break the build?
 
 ## 5. Output Guidelines (The Contract)
 
 ### Standard Implementation Report
+
 ```markdown
 ## Implementation: [Feature Name]
 
@@ -72,41 +84,59 @@ The command routes to specialized sub-agents based on the `--agent` flag or file
 ## 6. Examples
 
 ### A. Backend Feature
+
 ```bash
 /soc-implement "User Registration API" --agent backend
 ```
+
 *Effect:* `backend` agent writes `POST /register`, adds `UserSchema` validation, inputs into Postgres, and returns a sanitized User DTO.
 
 ### B. Frontend Component
+
 ```bash
 /soc-implement "DarkMode Toggle" --agent frontend
 ```
+
 *Effect:* `frontend` agent checks `tailwind.config.js`, creates a toggle component using `Radix UI` primitives (if installed) and handles local storage state.
 
 ## 7. Dependencies & Capabilities
 
 ### Agents
--   **Backend**: `@[.opencode/agents/backend.md]`
--   **Frontend**: `@[.opencode/agents/frontend.md]`
--   **Quality**: `@[.opencode/agents/quality.md]` - For TDD and verification.
+
+- **Backend**: `@[.opencode/agents/backend.md]`
+- **Frontend**: `@[.opencode/agents/frontend.md]`
+- **Quality**: `@[.opencode/agents/quality.md]` - For TDD and verification.
 
 ### Skills
--   **Confidence Check**: `@[.opencode/skills/confidence-check/SKILL.md]` - MANDATORY step before starting.
--   **Self Check**: `@[.opencode/skills/self-check/SKILL.md]` - Validation protocol after changes.
--   **Debug Protocol**: `@[.opencode/skills/debug-protocol/SKILL.md]` - If implementation hits errors.
+
+- **Confidence Check**: `@[.opencode/skills/confidence-check/SKILL.md]` - MANDATORY step before starting.
+- **Self Check**: `@[.opencode/skills/self-check/SKILL.md]` - Validation protocol after changes.
+- **Debug Protocol**: `@[.opencode/skills/debug-protocol/SKILL.md]` - If implementation hits errors.
+- **Package Manager**: `@[.opencode/skills/package-manager/SKILL.md]` - MANDATORY for all dependency operations.
+- **Simplification**: `@[.opencode/skills/simplification/SKILL.md]` - Keeps implementations minimal.
+- **Doc Sync**: `@[.opencode/skills/doc-sync/SKILL.md]` - Ensures documentation matches implementation.
 
 ### MCP Integration
--   **`context7`**: For looking up exact syntax and library API usage to prevent hallucinations.
--   **`filesystem`**: For determining current project structure and patterns.
+
+- **`context7`**: For looking up exact syntax and library API usage to prevent hallucinations.
+- **`filesystem`**: For determining current project structure and patterns.
+- **`tavily`**: Research latest best practices and library versions.
+- **`sequential-thinking`**: Step through complex implementation logic.
 
 ## 8. Boundaries
 
 **Will:**
--   Write code modules, tests, and documentation.
--   Fix compilation errors it causes.
--   Respect existing linters and formatters.
+
+- Write code modules, tests, and documentation.
+- Fix compilation errors it causes.
+- Respect existing linters and formatters.
 
 **Will Not:**
--   **Invent Designs**: If no design exists, it will fall back to simple best practices or ask for a design.
--   **Commit Violations**: Will not commit code with secrets or critical bugs.
--   **Touch Forbidden Files**: (e.g., `package-lock.json` manual edits, `.env` manual edits).
+
+- **Invent Designs**: If no design exists, it will fall back to simple best practices or ask for a design.
+- **Commit Violations**: Will not commit code with secrets or critical bugs.
+- **Touch Forbidden Files**: (e.g., `package-lock.json` manual edits, `.env` manual edits).
+
+## User Instruction
+
+The user have executed the `/soc-implement` command by parsing the user's arguments provided in `<user-instruction>$ARGUMENTS</user-instruction>`, then route to the appropriate specialized agent based on the extracted `--agent` flag (backend, frontend, quality, or fullstack), perform a confidence check by reviewing existing code and patterns before starting, write test cases first following TDD principles if applicable, implement the feature or component using appropriate file operations, run the project's build and test commands for verification, trigger the reflexion skill to analyze and fix any failures with a maximum of 3 retry attempts, conduct a post-flight self-check for debugging artifacts and input sanitization, and generate an implementation report documenting changes made, verification status, and key architectural decisions.