skills.rest
gwenwindflower
gwenwindflowerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

opencode-plugin-config

Automate OpenCode plugin authoring and configuration with YAML frontmatter and TypeScript.

9|Updated Feb 15, 2026
Search Tags:#automation#typescript#hooks#plugin#bun#opencode
One-click install
npx skills add https://github.com/gwenwindflower/dotfiles --skill opencode-plugin-config
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-plugin-config
Source: https://github.com/gwenwindflower/dotfiles/tree/main/dot_agents/exact_skills/opencode-plugin-config
Command: npx skills add https://github.com/gwenwindflower/dotfiles --skill opencode-plugin-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Author OpenCode plugins to automate actions tied to events (formatters after edits, pre-commit scripts, etc.). Use when adding or modifying OpenCode plugins. Skip for Claude Code automations (use claude-code-hooks-config).

Core Features & Use Cases

  • Defines how to structure OpenCode plugins and the types of automation (hooks, custom tools, loggers)
  • Helps decide whether a plugin is user-level (in ~/.opencode/plugins) or project-level (in <project root>/.opencode/plugins)
  • Guides building plugins in TypeScript with bun as the runtime for fast iteration
  • Provides a concrete use case: automating a pre-commit script within a project

Quick Start

Create or update an OpenCode plugin configuration in your project to automate events like post-edit formatting and pre-commit checks

Frequently Asked Questions about opencode-plugin-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tasks like formatting and pre-commit scripts with OpenCode plugins?▼

You can automate OpenCode plugin workflows by authoring plugins that bind actions to events like post-edit formatting and pre-commit checks. Configure them in TypeScript using bun as the runtime for fast iteration.

Should I configure my OpenCode plugin at the user level or project level?▼

OpenCode plugin configuration scope depends on your target: user-level plugins go in ~/.opencode/plugins, while project-level plugins reside in <project root>/.opencode/plugins to share automation across a specific repository.

What types of automation can I build using OpenCode plugins?▼

OpenCode plugins support automating actions tied to events through hooks, custom tools, and loggers. You can structure these automations to handle repetitive development tasks like running formatters after edits.

Do I need TypeScript and bun to create OpenCode plugins?▼

TypeScript with bun is the specified runtime guidance for building OpenCode plugins, providing fast iteration speeds. Your plugin files also require YAML frontmatter defining the plugin name and description.

Does this work for Claude Code hooks and automations?▼

No, this is specifically for OpenCode plugin configuration. You should skip this approach for Claude Code automations and use dedicated Claude Code hooks configuration tools instead.

Related Skills

Explore More Software Engineering Skills→
LiorCohenLiorCohen
39

agents-standards

Enforce standardized agent definitions with required YAML frontmatter and self-containment rules.

Community
Advanced
g-zenrg-zenr

setup-hooks

Configure automated code validation hooks for syntax, annotations, and tests.

Community
Intermediate
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
andrioidandrioid
8

mise-tasks

Organize and execute bash-based mise tasks from the scripts/ directory.

Community
Intermediate