Gestionnaire de Maintenance

VérifiéPrudence

Surveille les versions des outils de développement, vérifie les mises à jour disponibles pour Oh My Opencode et fournit des instructions de mise à niveau claires. Utile pour les questions sur la mise à jour, la vérification de version ou la maintenance des outils.

Spar Skills Guide Bot
DeveloppementDébutant
8002/06/2026
Claude Code
#tool-maintenance#version-check#upgrade#oh-my-opencode

Recommandé pour

Notre avis

Cette compétence surveille et met à jour les outils de développement, en commençant par Oh My Opencode, en vérifiant les versions et en fournissant des instructions de mise à niveau.

Points forts

  • Automatise la vérification des versions locales et distantes.
  • Fournit des commandes de mise à niveau claires et précises.
  • Préserve les fichiers de configuration lors des mises à jour.
  • Détecte les versions stables et bêta.

Limites

  • Limitée pour l'instant à Oh My Opencode uniquement.
  • Ne supporte pas les mises à jour automatiques, nécessite une intervention manuelle.
  • Ne couvre pas l'installation initiale ni le dépannage fonctionnel.
Quand l'utiliser

Utilisez cette compétence lorsque l'utilisateur demande comment vérifier ou mettre à jour la version d'Oh My Opencode.

Quand l'éviter

Ne l'utilisez pas pour installer Oh My Opencode pour la première fois ou pour résoudre des bugs non liés aux versions.

Analyse de sécurité

Prudence
Score qualité85/100

The skill instructs the AI agent to execute 'bunx oh-my-opencode ...' commands for version checks and upgrades. While intended for a legitimate maintenance tool, this involves network downloads and execution of code, which could be exploited if the package is malicious. No destructive or exfiltration actions are present, but the risk warrants caution.

Points d'attention
  • Instructs running 'bunx' commands, which downloads and executes code from npm; potential supply chain risk if the package is compromised.

Exemples

Check if Oh My Opencode is up to date
Is my Oh My Opencode installation up to date?
Upgrade to latest Oh My Opencode
How do I upgrade to the latest Oh My Opencode?

name: housekeeper description: Automatically triggers when users ask about upgrading, updating, or checking versions of Oh My Opencode or other development tools. Use for version checks, upgrade procedures, maintenance recommendations, and keeping development tools current. scope: global license: MIT

Housekeeper

What this skill does

The Housekeeper skill monitors and maintains your development tools, starting with Oh My Opencode. It checks current versions, identifies available updates, and provides clear upgrade instructions to keep your tools current.

When to use this skill

This skill automatically triggers when users ask about:

  • "upgrade", "update", or "check version" for Oh My Opencode
  • "is my tool up to date?", "how to update [tool name]"
  • "check for updates", "what's the latest version of [tool]"
  • General tool maintenance and version management queries

Never use this skill for:

  • Installing tools for the first time (use installation skills instead)
  • Questions about specific tool usage or features
  • Bug fixes or troubleshooting unrelated to versions

Instructions

For Oh My Opencode Maintenance:

  1. Check Current Status:

    • Run bunx oh-my-opencode get-local-version to check your current version
    • Compare against the latest available versions from npm
  2. Identify Update Type:

    • Determine if the latest version is stable or beta
    • Check release notes for breaking changes or new features
    • Consider your stability requirements (stable vs beta)
  3. Perform Upgrade:

    • For stable upgrades: bunx oh-my-opencode install
    • For specific versions: bunx oh-my-opencode@<version> install
    • For beta versions: bunx oh-my-opencode@3.0.0-beta.2 install
  4. Verify Installation:

    • Run bunx oh-my-opencode doctor to ensure everything works correctly
    • Confirm configuration files are preserved (oh-my-opencode.json, opencode.json)
  5. Provide Maintenance Recommendations:

    • Suggest regular update schedule (weekly/monthly)
    • Recommend testing major version upgrades in non-critical projects first
    • Advise on backing up configuration before major upgrades

Future Tool Support:

This skill will be extended to support additional development tools. The framework is designed to be extensible for:

  • Other OpenCode plugins
  • Development environment tools
  • Language-specific package managers
  • CLI utilities

Example Usage

User: "Is my Oh My Opencode installation up to date?"

Housekeeper Response:

  • Checks current version with bunx oh-my-opencode get-local-version
  • Compares against npm registry
  • Reports status and provides upgrade command if needed

User: "How do I upgrade to the latest Oh My Opencode?"

Housekeeper Response:

  • Identifies latest stable vs beta versions
  • Provides appropriate upgrade command
  • Explains any important considerations for the upgrade

Important Notes

  • Configuration Preservation: Your existing configuration files are preserved during upgrades
  • No Auto-Update: Manual intervention is required for all updates
  • Version Pinning: You can pin to specific versions if needed
  • Backup Recommended: Always backup configuration before major version upgrades
  • Stable vs Beta: Choose stable versions for production, beta for testing new features
Skills similaires