Sammlungen
Sammlung opencode

OpenCode-Workflow-Tools und Companion-Integrationen | AI Agent Skills

Installierbare AI Agent Skills für opencode companion integrations Developer Workflows in Claude Code, Cursor und Windsurf.

OpenCode-Workflows brauchen mehr als eine einfache Toolliste. Diese Sammlung hebt praxisnahe Skills, Integrationen und Automationskomponenten hervor, die reale Ergebnisse liefern: Codequalität, Dokumentationskonsistenz und reibungslosere Delivery-Prozesse. Teilweise gibt es MCP-Funktionen, der Hauptfokus liegt jedoch auf Entwickler-Workflows im Alltag.

Page-Level Review Standard

This Page Is a Curated Decision Surface, Not Just a Themed List

A collection page should not just add more cards to the screen. It should explain why these skills belong together, how the next step moves into installation and validation, and which path should continue the decision afterwards.

Reviewed On
2026-04-17
Maintained By
Maintained through Killer-Skills editorial review with install, documentation, and OpenCode workflow checks.
Verification
Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Primary Audience
High-intent users who roughly know the direction and need a faster path to an installable shortlist.

Three Minimum Standards For This Collection

  • - A collection page must narrow users into a better shortlist instead of flattening more repositories onto the screen.
  • - The next click should continue into installation docs, CLI validation, or a better-fit solution page instead of resetting back to a broad directory.
  • - This collection page works best when its selection logic, maintenance notes, and next steps are all clear.
Primary Install Bridge

Pick One Skill, Then Take the Install Path

This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from OpenCode workflow discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path
Best-Fit Next Paths

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution page, CLI docs, or the next collection that best matches this theme. That keeps platform, framework, and operations needs easier to compare and verify.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against OpenCode workflow fit, installation clarity, operator handoff, and day-to-day delivery usefulness. This page is now positioned as an install-first OpenCode entry point instead of a generic companion integrations list.

We prioritize this page because OpenCode-intent users usually need a shortlist they can install, validate, and carry into real development loops quickly.

Trust Signals

  • - Entries are chosen for practical OpenCode workflow value such as coding support, review loops, handoff, and repeatable execution.
  • - Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
  • - The page is curated for repeatable developer execution, not for vague companion-integration keyword stuffing.

Grouping Logic

  • - Lead with tools that can enter an OpenCode-centered workflow without adding heavy setup ambiguity.
  • - Keep the shortlist compact enough for quick comparison while still covering coding, review, handoff, and automation.
  • - Use installation as the bridge from OpenCode discovery into validated daily execution.

Maintenance & Review

Last Reviewed
2026-04-17
Cadence
Re-check when install flow, maintainer posture, or OpenCode workflow relevance changes upstream; otherwise review monthly.
Maintained By
Maintained through Killer-Skills editorial review with install, documentation, and OpenCode workflow checks.
Verification
Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Execution Examples

How These Skills Work Together In Practice

Install one OpenCode workflow companion first

Use this page when you want one OpenCode companion that can enter real development work without turning evaluation into another endless tooling loop.

  1. 1. Open the installation docs before opening more OpenCode-related repositories.
  2. 2. Choose one tool that best supports coding, review, handoff, or automation.
  3. 3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
  4. 4. Only after the base path works, expand the setup across the wider team workflow.

Reduce integration drag around OpenCode

Treat the collection as an editorial filter when you need OpenCode-adjacent tools that improve delivery quality without overcomplicating the stack.

  1. 1. Check whether the tool has stable ownership and visible install guidance.
  2. 2. Review CLI behavior so operators know what will be written and synced.
  3. 3. Use one validated path before scaling it to more projects or more teammates.
  4. 4. Document the chosen OpenCode workflow baseline after the first clean rollout.
After Installation

Supporting Moves After The Install Path Is Clear

sync-readme

Logo of lbb00
lbb00

Sync README ist eine Fähigkeit von KI-Agents, die README-Dokumente synchronisiert und übersetzt.

lore-field-repair

Logo of lorehq
lorehq

Guided workflow for diagnosing and fixing harness bugs in deployed instances

Related Collections

If This Page Is Close, Keep Narrowing With Related Collections

Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.

Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

Für welche Workflows sind diese Sammlungen gedacht?

Diese Sammlungen sind rund um Workflow-Automatisierung, Prozessautomatisierung, Dokumentenoperationen, Datenworkflows und wiederverwendbare Skill-Stacks aufgebaut.

Was unterscheidet eine Sammlung vom Hauptverzeichnis?

Das Verzeichnis eignet sich besser für direkte Suche, während Sammlungen komplementäre Skills um einen vollständigen Workflow bündeln.

Kann ich diese Sammlungen für Claude Code oder Cursor installieren?

Ja. Die Skills in diesen Sammlungen funktionieren in der Regel in Claude Code, Cursor, Windsurf und anderen unterstützten Umgebungen über einen einheitlichen Installationsablauf.

Additional Next Paths

Use These Additional Paths If You Need One More Step To Narrow The Decision

These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.