opencode-coder

Use this skill when the AI assistant should simplify recently changed files after implementation work, using recent-change scope guardrails and parallel reuse/quality/efficiency review lenses. Do not use this skill for whole-repository cleanup sweeps, architecture rewrites.

Use this skill for beads-centric planning, issue structure, execution orchestration, acceptance review gates, beads setup/runtime troubleshooting, beads health checks, and beads follow-up bug/task filing when users ask to capture tracker bugs/tasks (for example with repro and expected vs actual), even without explicitly saying beads. Trigger only for beads tracker workflow requests. Do not trigger for opencode-coder mode/runtime controls (stealth mode, team mode, OPENCODE_CODER_DISABLED), observability or production-log triage into bugs, external task-sync/import-export workflows (GitHub issues/Jira), docs lifecycle/taxonomy cleanup, simplify cleanup, GitHub releases, or general coding tasks.

Use this skill only for core opencode-coder plugin/runtime workflows: init/setup guidance, mode/runtime behavior, plugin-runtime status/doctor troubleshooting, plugin/runtime debug-log analysis, plugin/runtime bug reporting, and session dump export.

Use this skill whenever the user wants to create, refresh, review, reorganize, audit, slim, standardize, or fix project documentation; define canonical docs taxonomy; update AGENTS.md routing; or clean up stale, confusing, misrouted, or hollow docs. Trigger even when the user says things like 'our docs are messy,' 'does AGENTS still match the repo?,' 'help standardize the docs,' or 'review the docs before changing anything.'

GitHub backend for task synchronization. Syncs beads issues with GitHub issues bidirectionally using gh CLI. Use when: (1) User wants to sync with GitHub specifically, (2) Task-sync skill delegates to GitHub backend, (3) User mentions 'GitHub issues', 'gh sync', or 'import from GitHub'. Implements import (GitHub → beads), export (beads → GitHub), and bidirectional workflows.

Internal dev skill for working IN the opencode-coder plugin repo. Use when the AI assistant needs to: (1) Analyze OpenCode logs using the log-analyzer tool, (2) Run or understand dev commands (analyze-logs, fix-bugs, import-tasks, release), (3) Execute the release workflow, (4) Triage and import bugs from GitHub issues, (5) Understand plugin internals for development

Create or adapt skills for OpenCode, improve existing skills through iterative test-and-review loops, and package finished skills. Use when users want to author a skill from scratch, revise skill behavior, run qualitative/quantitative evaluations, or prepare a distributable .skill bundle.

Bidirectional synchronization between beads and external task systems (GitHub, Jira, etc.). Use when: (1) User wants to sync tasks or issues with external systems, (2) Import external issues into beads, (3) Export beads to external systems, (4) User mentions 'sync', 'GitHub issues', 'Jira tickets', 'import bugs', or 'export tasks'. Orchestrates workflow and delegates to backend-specific skills.

Use this skill whenever the user wants a skeptical complexity review of requirements, architecture or design proposals, pull requests, or code changes through principles of simplicity, justified abstraction, intellectual manageability, compatibility discipline, and hostility to accidental complexity. Use it when the task is to challenge complexity, justify abstractions, dependencies, or features, identify accidental complexity, or propose simplifications. Do not use it for implementation work, tracker workflows, or generic style-only review.

GitHub release workflow for any project. Use when: (1) User wants to create a GitHub release, (2) User asks about release process or versioning, (3) User mentions 'release', 'publish', 'ship', or 'version bump'. Handles quality gates, documentation validation, version management, and GitHub release creation.