askill
oc-update-command

oc-update-commandSafety 85Repository

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.

13 stars
1.2k downloads
Updated 3/10/2026

Package Files

Loading files...
SKILL.md

Update OpenCode Command

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.

Critical Rules

AskUserQuestion is MANDATORY

IMPORTANT: You MUST use the AskUserQuestion tool for ALL questions to the user. Never ask questions through regular text output.


Phase 1: Load References

Read the OpenCode platform overview and command guide:

  1. Read ${CLAUDE_PLUGIN_ROOT}/references/platform-overview.md
  2. Read ${CLAUDE_PLUGIN_ROOT}/references/command-guide.md

Phase 2: Locate Command

Find the command to update.

If $ARGUMENTS is provided:

  1. Check if the argument is a file path — read it directly
  2. If it's a command name — search for {name}.md in known directories

If no arguments:

  1. Search for OpenCode commands in the workspace:
    • Glob for .opencode/commands/*.md
    • Glob for ~/.config/opencode/commands/*.md
  2. Present found commands using AskUserQuestion:
    • Header: "Select Command"
    • Question: "Which command would you like to update?"
    • Options: List found commands (up to 4; include "Other" for custom path)

Read the selected command file and store its contents.


Phase 3: Research

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

Phase 4: Analyze

Compare the existing command against current best practices:

Frontmatter Issues

IssueDetectionFix
Wrong model formatMust be provider/model-id if presentConvert format
Skill-only frontmatterFields like user-invocable, name, allowed-toolsRemove
Missing descriptionShould have for command listingAdd
Unknown agent valueIf agent field present, agent must existVerify or remove
subtask typeMust be boolean if presentFix type

Body Issues

IssueDetectionFix
Inconsistent $VARIABLEsMixed case or invalid patternsStandardize to uppercase
Claude Code tool namesAskUserQuestion instead of questionConvert
mcp__ formatDouble-underscore MCP namingConvert to single-underscore
Hardcoded pathsSystem-specific absolute pathsConvert to relative, $VARIABLE, or @filepath reference
Very long bodyCommands should be concise workflow shortcutsSuggest splitting into a skill
Missing shell injectionCould use !`command` for dynamic contextSuggest where appropriate

Structure Issues

IssueDetectionFix
No clear stepsUnstructured instructionsAdd numbered steps
Missing output specificationNo description of expected outputAdd output section
Unused variables$VARIABLEs declared but never used in bodyRemove or use

Phase 5: Present Findings

Present the analysis:

## Update Analysis: {command-name}

### Errors (must fix)
{list}

### Warnings (should fix)
{list}

### Suggestions
{list}

### Research Notes
{findings}

Use AskUserQuestion for approval:

  • Header: "Apply Updates"
  • Question: "Would you like to apply these updates?"
  • Options:
    • "Apply all"
    • "Errors and warnings only"
    • "Errors only"
    • "Cancel"
  • multiSelect: false

Phase 6: Apply Updates

Apply changes based on user selection:

  1. Use Edit to modify the command file
  2. Fix frontmatter first, then body content
  3. Preserve the command's intent

Phase 7: Validate

Spawn 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.

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

78/100Analyzed 3/27/2026

Well-structured skill with 7 clearly defined phases, comprehensive issue tables, and proper safety patterns. Excellent actionability and clarity with structured steps. Reusability limited by project-specific references (CLAUDE_PLUGIN_ROOT, agent-alchemy agent types). Internal-only due to deep nesting and specialized OpenCode platform focus, but professionally written.

85
90
45
82
88

Metadata

Licenseunknown
Version-
Updated3/10/2026
Publishersequenzia

Tags

github-actionsllmprompting