analyze-coverage
FreeAnalyze test coverage and identify gaps with actionable recommendations
The English summary is being prepared. Showing the original description.
Updates an existing OpenCode command to match current platform best practices, fixes deprecated patterns, and validates the result. Use when user says "update opencode command", "fix opencode command", "migrate command to opencode", or wants to modernize an existing OpenCode command file.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are initiating the OpenCode command update workflow. This process locates an existing command, researches current platform best practices, analyzes the command for issues, and applies updates with validation.
IMPORTANT: You MUST use the AskUserQuestion tool for ALL questions to the user. Never ask questions through regular text output.
Read the OpenCode platform overview and command guide:
${CLAUDE_PLUGIN_ROOT}/references/platform-overview.md${CLAUDE_PLUGIN_ROOT}/references/command-guide.mdFind the command to update.
If $ARGUMENTS is provided:
{name}.md in known directoriesIf no arguments:
Glob for .opencode/commands/*.mdGlob for ~/.config/opencode/commands/*.mdAskUserQuestion:
Read the selected command file and store its contents.
Spawn the researcher agent to check latest documentation:
Task:
subagent_type: "agent-alchemy-opencode-tools:oc-researcher"
prompt: |
Research the latest OpenCode documentation for command format compatibility.
Artifact type: command
Current artifact content:
---
{contents of the command file}
---
Specific questions:
1. Are there any new command frontmatter fields?
2. Has the $VARIABLE system changed?
3. Are there new command discovery paths?
4. Any changes to the model override behavior?
Reference guide: ${CLAUDE_PLUGIN_ROOT}/references/command-guide.md
Compare the existing command against current best practices:
| Issue | Detection | Fix |
|---|---|---|
| Wrong model format | Must be provider/model-id if present | Convert format |
| Skill-only frontmatter | Fields like user-invocable, name, allowed-tools | Remove |
Missing description | Should have for command listing | Add |
Unknown agent value | If agent field present, agent must exist | Verify or remove |
subtask type | Must be boolean if present | Fix type |
| Issue | Detection | Fix |
|---|---|---|
| Inconsistent $VARIABLEs | Mixed case or invalid patterns | Standardize to uppercase |
| Claude Code tool names | AskUserQuestion instead of question | Convert |
mcp__ format | Double-underscore MCP naming | Convert to single-underscore |
| Hardcoded paths | System-specific absolute paths | Convert to relative, $VARIABLE, or @filepath reference |
| Very long body | Commands should be concise workflow shortcuts | Suggest splitting into a skill |
| Missing shell injection | Could use !`command` for dynamic context | Suggest where appropriate |
| Issue | Detection | Fix |
|---|---|---|
| No clear steps | Unstructured instructions | Add numbered steps |
| Missing output specification | No description of expected output | Add output section |
| Unused variables | $VARIABLEs declared but never used in body | Remove or use |
Present the analysis:
## Update Analysis: {command-name}
### Errors (must fix)
{list}
### Warnings (should fix)
{list}
### Suggestions
{list}
### Research Notes
{findings}
Use AskUserQuestion for approval:
Apply changes based on user selection:
Edit to modify the command fileSpawn the validator agent:
Task:
subagent_type: "agent-alchemy-opencode-tools:oc-validator"
prompt: |
Validate the following OpenCode artifact:
Type: command
Path: {path to updated file}
Reference guide: ${CLAUDE_PLUGIN_ROOT}/references/command-guide.md
Present validation results and a before/after summary.
CRITICAL: Complete ALL 7 phases before finishing.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Analyze test coverage and identify gaps with actionable recommendations
The English summary is being prepared. Showing the original description.
Analyze an existing spec for inconsistencies, missing information, ambiguities, and structure issues. Use when user says "analyze spec", "review spec", "spec quality check", "validate requirements", "audit spec", or "check spec quality".
The English summary is being prepared. Showing the original description.
Provides architectural pattern knowledge for designing feature implementations including MVC, event-driven, microservices, and CQRS patterns. Use when designing system architecture or choosing implementation patterns.
The English summary is being prepared. Showing the original description.
Executes diagnostic investigation tasks to test debugging hypotheses. Runs tests, traces execution, checks git history, and reports evidence. (converted from agent)
The English summary is being prepared. Showing the original description.
Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use when asked to "fix this bug", "debug this", "why is this failing", "this is broken", "investigate this error", "track down this issue", or any debugging situation. Supports --deep flag to force full investigation.
The English summary is being prepared. Showing the original description.
Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use for debugging, fixing bugs, and investigating errors.
The English summary is being prepared. Showing the original description.