opencode-mirror
$
npx mdskill add different-ai/openwork/opencode-mirrorMaintains a local mirror of the OpenCode repository for reference
- Synchronizes the local OpenCode mirror with upstream changes
- Uses Git commands to clone and pull from the official OpenCode GitHub repository
- Applies fast-forward-only merges to preserve a clean commit history
- Stores the mirrored repository in the `vendor/opencode` directory
SKILL.md
.github/skills/opencode-mirrorView on GitHub ↗
--- name: opencode-mirror description: Maintain the local OpenCode mirror for self-reference --- ## Quick Usage (Already Configured) ### Update mirror ```bash git -C vendor/opencode pull --ff-only ``` ## Common Gotchas - Keep the mirror gitignored; never commit `vendor/opencode`. - Use `--ff-only` to avoid merge commits in the mirror. ## First-Time Setup (If Not Configured) ### Clone mirror ```bash git clone https://github.com/anomalyco/opencode vendor/opencode ```
More from different-ai/openwork
- browser-setup-devtoolsGuide users through browser automation setup using Chrome DevTools MCP only. Use when the user asks to set up browser automation, Chrome DevTools MCP, browser MCP, or runs the browser-setup command.
- daytona-electron-testTest the real Electron app on Daytona: create sandbox, start services, connect via CDP, create workspaces, drive sessions, and verify settings. Use when the user says 'test on Daytona', 'run the app on Daytona', 'Daytona dry run', 'test Electron remotely', or 'reproduce on Daytona'.
- get-startedGuide users through the get started setup and Chrome DevTools demo.
- opencode-bridgeBridge between OpenWork UI and OpenCode runtime
- opencode-primitivesReference OpenCode docs when implementing skills, plugins, MCPs, or config-driven behavior.
- openwork-coreCore context and guardrails for OpenWork native app
- openwork-debugDebug OpenWork sidecars, config, and audit trail
- openwork-orchestrator-npm-publish|
- run-evalsRun OpenWork UI evals on a Daytona sandbox or local Electron instance. Handles sandbox creation, service startup, and eval execution via CDP browser tools.
- shadcnManages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".