agentsys 5.0.2 → 5.1.0

package/adapters/opencode/skills/consult/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: consult
 description: "Cross-tool AI consultation. Use when user asks to 'consult gemini', 'ask codex', 'get second opinion', 'cross-check with claude', 'consult another AI', 'ask opencode', 'copilot opinion', or wants a second opinion from a different AI tool."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[question] [--tool] [--effort] [--model] [--context] [--continue]"
 ---
 
@@ -67,37 +66,41 @@ Command: gemini -p "QUESTION" --output-format json -m "MODEL"
 Session resume: --resume "SESSION_ID"
 ```
 
-Models: gemini-2.5-flash, gemini-2.5-pro, gemini-3-flash-preview, gemini-3-pro-preview
+Models: gemini-2.5-flash, gemini-2.5-pro, gemini-3-flash, gemini-3-pro
 
 | Effort | Model |
 |--------|-------|
 | low | gemini-2.5-flash |
-| medium | gemini-2.5-pro |
-| high | gemini-3-flash-preview |
-| max | gemini-3-pro-preview |
+| medium | gemini-3-flash |
+| high | gemini-3-pro |
+| max | gemini-3-pro |
 
 **Parse output**: `JSON.parse(stdout).response`
+**Session ID**: `JSON.parse(stdout).session_id`
 **Continuable**: Yes (via `--resume`)
 
 ### Codex
 
 ```
-Command: codex -q "QUESTION" --json -m "MODEL" -a suggest -c model_reasoning_effort="LEVEL"
-Session resume: codex resume "SESSION_ID"
+Command: codex exec "QUESTION" --json -m "MODEL" -c model_reasoning_effort="LEVEL"
+Session resume: codex exec resume SESSION_ID "QUESTION" --json
+Session resume (latest): codex exec resume --last "QUESTION" --json
 ```
 
-Models: gpt-5.1-codex-mini, gpt-5-codex, gpt-5.1-codex, gpt-5.2-codex, gpt-5.3-codex, gpt-5.1-codex-max
+Note: `codex exec` is the non-interactive/headless mode. There is no `-q` flag. The TUI mode is `codex` (no subcommand).
+
+Models: gpt-5.3-codex-spark, gpt-5-codex, gpt-5.1-codex, gpt-5.2-codex, gpt-5.3-codex, gpt-5.1-codex-max
 
 | Effort | Model | Reasoning |
 |--------|-------|-----------|
-| low | gpt-5.1-codex-mini | low |
+| low | gpt-5.3-codex-spark | low |
 | medium | gpt-5.2-codex | medium |
 | high | gpt-5.3-codex | high |
 | max | gpt-5.3-codex | xhigh |
 
 **Parse output**: `JSON.parse(stdout).message` or raw text
 **Session ID**: Codex prints a resume hint at session end (e.g., `codex resume SESSION_ID`). Extract the session ID from stdout or from `JSON.parse(stdout).session_id` if available.
-**Continuable**: Yes, but interactive only. Sessions are stored as JSONL rollout files at `~/.codex/sessions/`. The `codex resume SESSION_ID` subcommand resumes in TUI mode -- it does not support `-q` for non-interactive use. For non-interactive continuation, prepend prior conversation context to the new question text instead.
+**Continuable**: Yes. Sessions are stored as JSONL rollout files at `~/.codex/sessions/`. Non-interactive resume uses `codex exec resume SESSION_ID "follow-up prompt" --json`. Use `--last` instead of a session ID to resume the most recent session.
 
 ### OpenCode
 
@@ -162,7 +165,7 @@ Use the command template from the provider's configuration section. Substitute Q
 
 If continuing a session:
 - **Claude or Gemini**: append `--resume SESSION_ID` to the command.
-- **Codex**: no non-interactive resume flag exists. Prepend the prior Q&A context to the new question text before passing to `codex -q`.
+- **Codex**: use `codex exec resume SESSION_ID "QUESTION" --json` instead of the standard command. Use `--last` instead of a session ID for the most recent session.
 - **OpenCode**: append `--session SESSION_ID` to the command. If no session_id is saved, use `--continue` instead (resumes most recent session).
 If OpenCode at max effort: append `--thinking`.
 
@@ -180,7 +183,7 @@ User-provided question text MUST NOT be interpolated into shell command strings.
 1. **Write the question** to a temporary file using the Write tool (e.g., `{AI_STATE_DIR}/consult/question.tmp`)
 
    Platform state directory:
-   - Claude Code: `.opencode/`
+   - Claude Code: `.claude/`
    - OpenCode: `.opencode/`
    - Codex CLI: `.codex/`
 2. **Build the command** using the temp file as input instead of inline text:
@@ -191,8 +194,9 @@ User-provided question text MUST NOT be interpolated into shell command strings.
 | Claude (resume) | `claude -p - --output-format json --model "MODEL" --max-turns TURNS --allowedTools "Read,Glob,Grep" --resume "SESSION_ID" < "{AI_STATE_DIR}/consult/question.tmp"` |
 | Gemini | `gemini -p - --output-format json -m "MODEL" < "{AI_STATE_DIR}/consult/question.tmp"` |
 | Gemini (resume) | `gemini -p - --output-format json -m "MODEL" --resume "SESSION_ID" < "{AI_STATE_DIR}/consult/question.tmp"` |
-| Codex | `codex -q "$(cat "{AI_STATE_DIR}/consult/question.tmp")" --json -m "MODEL" -a suggest` (Codex lacks stdin mode -- cat reads from platform-controlled path, not user input) |
-| Codex (continue) | No non-interactive resume. Prepend prior context to question, then use standard Codex command above. |
+| Codex | `codex exec "$(cat "{AI_STATE_DIR}/consult/question.tmp")" --json -m "MODEL" -c model_reasoning_effort="LEVEL"` (Codex exec lacks stdin mode -- cat reads from platform-controlled path, not user input) |
+| Codex (resume) | `codex exec resume SESSION_ID "$(cat "{AI_STATE_DIR}/consult/question.tmp")" --json -m "MODEL"` |
+| Codex (resume latest) | `codex exec resume --last "$(cat "{AI_STATE_DIR}/consult/question.tmp")" --json -m "MODEL"` |
 | OpenCode | `opencode run - --format json --model "MODEL" --variant "VARIANT" < "{AI_STATE_DIR}/consult/question.tmp"` |
 | OpenCode (resume by ID) | `opencode run - --format json --model "MODEL" --variant "VARIANT" --session "SESSION_ID" < "{AI_STATE_DIR}/consult/question.tmp"` |
 | OpenCode (resume latest) | `opencode run - --format json --model "MODEL" --variant "VARIANT" --continue < "{AI_STATE_DIR}/consult/question.tmp"` |
@@ -230,7 +234,7 @@ After successful consultation, save to `{AI_STATE_DIR}/consult/last-session.json
 ```
 
 `AI_STATE_DIR` uses the platform state directory:
-- Claude Code: `.opencode/`
+- Claude Code: `.claude/`
 - OpenCode: `.opencode/`
 - Codex CLI: `.codex/`
 
@@ -245,16 +249,26 @@ If session file not found, warn and proceed as fresh consultation.
 
 ## Output Sanitization
 
-Before returning the response, the invoking agent MUST scan for and redact API keys, tokens, and credentials that may appear in the consulted tool's output. At minimum, redact these patterns:
-
-- `sk-[a-zA-Z0-9_-]{20,}` and `sk-ant-*`, `sk-proj-*` (API keys)
-- `AIza[a-zA-Z0-9_-]{30,}` (Google API keys)
-- `AKIA*`, `ASIA*` (AWS access/session keys)
-- `ghp_*`, `gho_*`, `github_pat_*` (GitHub tokens)
-- `ANTHROPIC_API_KEY=*`, `OPENAI_API_KEY=*`, `GOOGLE_API_KEY=*`, `GEMINI_API_KEY=*` (env assignments)
-- `Bearer [a-zA-Z0-9_-]{20,}` (auth headers)
-
-See `consult-agent.md` for the complete redaction pattern table with replacements.
+Before including any consulted tool's response in the output, scan the response text and redact matches for these patterns:
+
+| Pattern | Description | Replacement |
+|---------|-------------|-------------|
+| `sk-[a-zA-Z0-9_-]{20,}` | Anthropic API keys | `[REDACTED_API_KEY]` |
+| `sk-proj-[a-zA-Z0-9_-]{20,}` | OpenAI project keys | `[REDACTED_API_KEY]` |
+| `sk-ant-[a-zA-Z0-9_-]{20,}` | Anthropic API keys (ant prefix) | `[REDACTED_API_KEY]` |
+| `AIza[a-zA-Z0-9_-]{30,}` | Google API keys | `[REDACTED_API_KEY]` |
+| `ghp_[a-zA-Z0-9]{36,}` | GitHub personal access tokens | `[REDACTED_TOKEN]` |
+| `gho_[a-zA-Z0-9]{36,}` | GitHub OAuth tokens | `[REDACTED_TOKEN]` |
+| `github_pat_[a-zA-Z0-9_]{20,}` | GitHub fine-grained PATs | `[REDACTED_TOKEN]` |
+| `ANTHROPIC_API_KEY=[^\s]+` | Key assignment in env output | `ANTHROPIC_API_KEY=[REDACTED]` |
+| `OPENAI_API_KEY=[^\s]+` | Key assignment in env output | `OPENAI_API_KEY=[REDACTED]` |
+| `GOOGLE_API_KEY=[^\s]+` | Key assignment in env output | `GOOGLE_API_KEY=[REDACTED]` |
+| `GEMINI_API_KEY=[^\s]+` | Key assignment in env output | `GEMINI_API_KEY=[REDACTED]` |
+| `AKIA[A-Z0-9]{16}` | AWS access keys | `[REDACTED_AWS_KEY]` |
+| `ASIA[A-Z0-9]{16}` | AWS session tokens | `[REDACTED_AWS_KEY]` |
+| `Bearer [a-zA-Z0-9_-]{20,}` | Authorization headers | `Bearer [REDACTED]` |
+
+Apply redaction to the full response text before inserting into the result JSON. If any redaction occurs, append a note: `[WARN] Sensitive tokens were redacted from the response.`
 
 ## Output Format
 
@@ -263,7 +277,7 @@ Return a plain JSON object to stdout (no markers or wrappers):
 ```json
 {
   "tool": "gemini",
-  "model": "gemini-3-pro-preview",
+  "model": "gemini-3-pro",
   "effort": "high",
   "duration_ms": 12300,
   "response": "The AI's response text here...",

package/adapters/opencode/skills/debate/SKILL.md

@@ -0,0 +1,245 @@
+---
+name: debate
+description: "Structured AI debate templates and synthesis. Use when orchestrating multi-round debates between AI tools, 'debate topic', 'argue about', 'stress test idea', 'devil advocate'."
+version: 5.1.0
+argument-hint: "[topic] [--proposer=tool] [--challenger=tool] [--rounds=N] [--effort=level]"
+---
+
+> **OpenCode Note**: Invoke agents using `@agent-name` syntax.
+> Available agents: task-discoverer, exploration-agent, planning-agent,
+> implementation-agent, deslop-agent, delivery-validator, sync-docs-agent, consult-agent
+> Example: `@exploration-agent analyze the codebase`
+
+
+# debate
+
+Prompt templates, context assembly rules, and synthesis format for structured multi-round debates between AI tools.
+
+## Arguments
+
+Parse from `$ARGUMENTS`:
+- **topic**: The debate question/topic (required)
+- **--proposer**: Tool for the proposer role (claude, gemini, codex, opencode, copilot)
+- **--challenger**: Tool for the challenger role (must differ from proposer)
+- **--rounds**: Number of back-and-forth rounds (1-5, default: 2)
+- **--effort**: Thinking effort applied to all tool invocations (low, medium, high, max)
+- **--model-proposer**: Specific model for proposer (optional)
+- **--model-challenger**: Specific model for challenger (optional)
+
+## Universal Rules
+
+ALL participants (proposer AND challenger) MUST support claims with specific evidence (file path, code pattern, benchmark, or documented behavior). Unsupported claims from either side will be flagged by the other participant and noted in the verdict. This applies to every round.
+
+## Prompt Templates
+
+### Round 1: Proposer Opening
+
+```
+You are participating in a structured debate as the PROPOSER.
+
+Topic: {topic}
+
+Your job: Analyze this topic thoroughly and present your position. Take a clear stance. Do not hedge excessively.
+
+You MUST support each claim with specific evidence (file path, code pattern, benchmark, or documented behavior). Unsupported claims will be challenged. "I think" or "generally speaking" without evidence is not acceptable.
+
+Provide your analysis:
+```
+
+### Round 1: Challenger Response
+
+```
+You are participating in a structured debate as the CHALLENGER.
+
+Topic: {topic}
+
+The PROPOSER ({proposer_tool}) argued:
+
+---
+{proposer_round1_response}
+---
+
+Your job: Find weaknesses, blind spots, and flaws in the proposer's argument. You MUST identify at least one genuine flaw or overlooked consideration before agreeing on anything. Propose concrete alternatives where you disagree.
+
+Rules:
+- Do NOT say "great point" or validate the proposer's reasoning before critiquing it
+- Lead with what's WRONG or MISSING, then acknowledge what's right
+- If you genuinely agree on a point, explain what RISK remains despite the agreement
+- Propose at least one concrete alternative approach
+- You MUST address at least these categories: correctness, security implications, and developer experience
+- Do NOT agree with ANY claim unless you can cite specific evidence (file path, code pattern, or documented behavior) that supports the agreement. Unsupported agreement is not allowed.
+- If the proposer makes a claim without evidence, call it out: "This claim is unsupported."
+
+Provide your challenge:
+```
+
+### Round 2+: Proposer Defense
+
+```
+You are the PROPOSER in round {round} of a structured debate.
+
+Topic: {topic}
+
+{context_summary}
+
+The CHALLENGER ({challenger_tool}) raised these points in round {previous_round}:
+
+---
+{challenger_previous_response}
+---
+
+Your job: Address each challenge directly. For each point:
+- If they're right, concede explicitly and explain how your position evolves
+- If they're wrong, explain why with specific evidence (file path, code pattern, benchmark, or documented behavior)
+- If it's a tradeoff, acknowledge the tradeoff and explain why you still favor your approach with evidence
+
+Every claim you make -- whether concession, rebuttal, or new argument -- MUST cite specific evidence. The challenger will reject unsupported claims.
+
+Do NOT simply restate your original position. Your response must show you engaged with the specific challenges raised.
+
+Provide your defense:
+```
+
+### Round 2+: Challenger Follow-up
+
+*(JavaScript reference - not executable in OpenCode)*
+
+## Context Assembly
+
+### Rounds 1-2: Full context
+
+Include the full text of all prior exchanges in the prompt. Context is small enough (typically under 5000 tokens total).
+
+Format for context block:
+```
+Previous exchanges:
+
+Round 1 - Proposer ({proposer_tool}):
+{full response}
+
+Round 1 - Challenger ({challenger_tool}):
+{full response}
+```
+
+### Round 3+: Summarized context
+
+For rounds 3 and beyond, replace full exchange text from rounds 1 through N-2 with a summary. Only include the most recent round's responses in full.
+
+Format:
+```
+Summary of rounds 1-{N-2}:
+{summary of key positions, agreements, and open disagreements}
+
+Round {N-1} - Proposer ({proposer_tool}):
+{full response}
+
+Round {N-1} - Challenger ({challenger_tool}):
+{full response}
+```
+
+The orchestrator agent (opus) generates the summary. Target: 500-800 tokens. MUST preserve:
+- Each side's core position
+- All concessions (verbatim quotes, not paraphrased)
+- All evidence citations that support agreements
+- Points of disagreement (unresolved)
+- Any contradictions between rounds (e.g., proposer concedes in round 1 but walks it back in round 2 -- note both explicitly)
+
+## Synthesis Format
+
+After all rounds complete, the orchestrator produces this structured output:
+
+```
+## Debate Summary
+
+**Topic**: {topic}
+**Proposer**: {proposer_tool} ({proposer_model})
+**Challenger**: {challenger_tool} ({challenger_model})
+**Rounds**: {rounds_completed}
+**Rigor**: Structured perspective comparison (prompt-enforced adversarial rules, no deterministic verification)
+
+### Verdict
+
+{winner_tool} had the stronger argument because: {specific reasoning citing debate evidence}
+
+### Debate Quality
+
+Rate the debate on these dimensions:
+- **Genuine disagreement**: Did the challenger maintain independent positions, or converge toward the proposer? (high/medium/low)
+- **Evidence quality**: Did both sides cite specific examples, or argue from generalities? (high/medium/low)
+- **Challenge depth**: Were the challenges substantive, or surface-level? (high/medium/low)
+
+### Key Agreements
+- {agreed point 1} (evidence: {what supports this agreement})
+- {agreed point 2} (evidence: {what supports this agreement})
+
+### Key Disagreements
+- {point}: {proposer_tool} argues {X}, {challenger_tool} argues {Y}
+
+### Unresolved Questions
+- {question that neither side adequately addressed}
+
+### Recommendation
+{Orchestrator's recommendation - must pick a direction, not "both have merit"}
+```
+
+**Synthesis rules:**
+- The verdict MUST pick a side. "Both approaches have merit" is NOT acceptable.
+- Cite specific arguments from the debate as evidence for the verdict.
+- The recommendation must be actionable - what should the user DO based on this debate.
+- Unresolved questions highlight where the debate fell short, not where both sides are "equally valid."
+
+## State File Schema
+
+Save to `{AI_STATE_DIR}/debate/last-debate.json`:
+
+```json
+{
+  "id": "debate-{ISO timestamp}-{4 char random hex}",
+  "topic": "original topic text",
+  "proposer": {"tool": "claude", "model": "opus"},
+  "challenger": {"tool": "gemini", "model": "gemini-3-pro"},
+  "effort": "high",
+  "rounds_completed": 2,
+  "max_rounds": 2,
+  "status": "completed",
+  "exchanges": [
+    {"round": 1, "role": "proposer", "tool": "claude", "response": "...", "duration_ms": 8500},
+    {"round": 1, "role": "challenger", "tool": "gemini", "response": "...", "duration_ms": 12000},
+    {"round": 2, "role": "proposer", "tool": "claude", "response": "...", "duration_ms": 9200},
+    {"round": 2, "role": "challenger", "tool": "gemini", "response": "...", "duration_ms": 11000}
+  ],
+  "verdict": {
+    "winner": "claude",
+    "reasoning": "...",
+    "agreements": ["..."],
+    "disagreements": ["..."],
+    "recommendation": "..."
+  },
+  "timestamp": "{ISO 8601 timestamp}"
+}
+```
+
+Platform state directory:
+- Claude Code: `.claude/`
+- OpenCode: `.opencode/`
+- Codex CLI: `.codex/`
+
+## Error Handling
+
+| Error | Action |
+|-------|--------|
+| Proposer fails round 1 | Abort debate. Cannot proceed without opening position. |
+| Challenger fails round 1 | Show proposer's position with note: "[WARN] Challenger failed. Showing proposer's uncontested position." |
+| Any tool fails mid-debate | Synthesize from completed rounds. Note incomplete round in output. |
+| All rounds timeout | "[ERROR] Debate failed: all tool invocations timed out." |
+
+## Consult Skill Integration
+
+Each tool invocation uses the existing `consult` skill from the consult plugin. The orchestrator invokes it as:
+
+```
+Skill: consult
+Args: "{debate prompt with context}" --tool={tool} --effort={effort} --model={model}
+```
+
+The consult skill handles: provider command building, safe question passing (temp file), output parsing, and secret redaction. The debate skill does NOT duplicate this logic.

package/adapters/opencode/skills/deslop/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: deslop
 description: "Use when user wants to clean AI slop from code. Use for cleanup, remove debug statements, find ghost code, repo hygiene."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[report|apply] [--scope=all|diff|path] [--thoroughness=quick|normal|deep]"
 ---
 

package/adapters/opencode/skills/discover-tasks/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: discover-tasks
 description: "Use when user asks to \"discover tasks\", \"find next task\", or \"prioritize issues\". Discovers and ranks tasks from GitHub, GitLab, local files, and custom sources."
-version: 5.0.2
+version: 5.1.0
 ---
 
 # discover-tasks

package/adapters/opencode/skills/drift-analysis/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: drift-analysis
 description: Use when the user asks about plan drift, reality check, comparing docs to code, project state analysis, roadmap alignment, implementation gaps, or needs guidance on identifying discrepancies between documented plans and actual implementation state.
-version: 5.0.2
+version: 5.1.0
 ---
 
 # Drift Analysis

package/adapters/opencode/skills/enhance-agent-prompts/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-agent-prompts
 description: "Use when improving agent prompts, frontmatter, and tool restrictions."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[path] [--fix] [--verbose]"
 ---
 

package/adapters/opencode/skills/enhance-claude-memory/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-claude-memory
 description: "Use when improving CLAUDE.md or AGENTS.md project memory files."
-version: 5.0.2
+version: 5.1.0
 ---
 
 > **OpenCode Note**: Invoke agents using `@agent-name` syntax.

package/adapters/opencode/skills/enhance-cross-file/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-cross-file
 description: "Use when checking cross-file consistency: tools vs frontmatter, agent references, duplicate rules, contradictions."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[path]"
 ---
 

package/adapters/opencode/skills/enhance-docs/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-docs
 description: "Use when improving documentation structure, accuracy, and RAG readiness."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[path] [--fix] [--ai]"
 ---
 

package/adapters/opencode/skills/enhance-hooks/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-hooks
 description: "Use when reviewing hooks for safety, timeouts, and correct frontmatter."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[path] [--fix]"
 ---
 

package/adapters/opencode/skills/enhance-orchestrator/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-orchestrator
 description: "Use when coordinating multiple enhancers for /enhance command. Runs analyzers in parallel and produces unified report."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[path] [--apply] [--focus=TYPE]"
 ---
 

package/adapters/opencode/skills/enhance-plugins/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-plugins
 description: "Use when analyzing plugin structures, MCP tools, and plugin security patterns."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[path] [--fix]"
 ---
 

package/adapters/opencode/skills/enhance-prompts/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-prompts
 description: "Use when improving general prompts for structure, examples, and constraints."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[path] [--fix]"
 ---
 

package/adapters/opencode/skills/enhance-skills/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance-skills
 description: "Use when reviewing SKILL.md files for structure and trigger quality."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[path] [--fix]"
 ---
 

package/adapters/opencode/skills/learn/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: learn
 description: "Research any topic online and create learning guides. Use when user asks to 'learn about', 'research topic', 'create learning guide', 'build knowledge base', or 'study subject'."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[topic] [--depth=brief|medium|deep]"
 ---
 

package/adapters/opencode/skills/orchestrate-review/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: orchestrate-review
 description: "Use when user asks to \"deep review the code\", \"thorough code review\", \"multi-pass review\", or when orchestrating the Phase 9 review loop. Provides review pass definitions (code quality, security, performance, test coverage), signal detection patterns, and iteration algorithms."

package/adapters/opencode/skills/perf-analyzer/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf-analyzer
 description: "Use when synthesizing perf findings into evidence-backed recommendations and decisions."
-version: 5.0.2
+version: 5.1.0
 ---
 
 # perf-analyzer

package/adapters/opencode/skills/perf-baseline-manager/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf-baseline-manager
 description: "Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version."
-version: 5.0.2
+version: 5.1.0
 ---
 
 # perf-baseline-manager

package/adapters/opencode/skills/perf-benchmarker/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf-benchmarker
 description: "Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[command] [duration]"
 ---
 

package/adapters/opencode/skills/perf-code-paths/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf-code-paths
 description: "Use when mapping code paths, entrypoints, and likely hot files before profiling."
-version: 5.0.2
+version: 5.1.0
 ---
 
 # perf-code-paths

package/adapters/opencode/skills/perf-investigation-logger/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf-investigation-logger
 description: "Use when appending structured perf investigation notes and evidence."
-version: 5.0.2
+version: 5.1.0
 ---
 
 # perf-investigation-logger

package/adapters/opencode/skills/perf-profiler/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf-profiler
 description: "Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[tool] [command]"
 ---
 

package/adapters/opencode/skills/perf-theory-gatherer/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf-theory-gatherer
 description: "Use when generating performance hypotheses backed by git history and code evidence."
-version: 5.0.2
+version: 5.1.0
 ---
 
 # perf-theory-gatherer

package/adapters/opencode/skills/perf-theory-tester/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf-theory-tester
 description: "Use when running controlled perf experiments to validate hypotheses."
-version: 5.0.2
+version: 5.1.0
 ---
 
 # perf-theory-tester

package/adapters/opencode/skills/repo-mapping/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: repo-mapping
 description: "Use when user asks to \"create repo map\", \"generate repo map\", \"update repo map\", \"repo map status\", or \"map symbols/imports\". Builds and validates an AST-based repo map using ast-grep."
@@ -30,7 +29,7 @@ Build and maintain a cached AST-based map of repository symbols and imports usin
 
 Repo map is stored in the platform state directory:
 
-- Claude Code: `.opencode/repo-map.json`
+- Claude Code: `.claude/repo-map.json`
 - OpenCode: `.opencode/repo-map.json`
 - Codex CLI: `.codex/repo-map.json`
 

package/adapters/opencode/skills/sync-docs/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: sync-docs
 description: "Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes."
-version: 5.0.2
+version: 5.1.0
 argument-hint: "[report|apply] [--scope=all|recent|before-pr] [--include-undocumented]"
 allowed-tools: Bash(git:*), Read, Grep, Glob
 ---