Skip to content
cccskills
FreePublished on GitHub

oc-update-command

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 install

Files included (1)

  • SKILL.md4.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Analyze test coverage and identify gaps with actionable recommendations

The English summary is being prepared. Showing the original description.

sequenzia/agent-alchemy45Updated Jun 1, 2026

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.

sequenzia/agent-alchemy45Updated Jun 1, 2026

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.

sequenzia/agent-alchemy45Updated Jun 1, 2026

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.

sequenzia/agent-alchemy45Updated Jun 1, 2026

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.

sequenzia/agent-alchemy45Updated Jun 1, 2026

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.

sequenzia/agent-alchemy45Updated Jun 1, 2026

See all skills by sequenzia

Report a problem with this skill