컬렉션 opencode

OpenCode 워크플로우 도구 & 컴패니언 연동 | AI Agent Skills

Claude Code, Cursor, Windsurf용 opencode companion integrations AI Agent Skills 모음입니다. 개발자 워크플로 자동화에 초점을 둡니다.

OpenCode 워크플로우에는 단순한 도구 목록 이상의 접근이 필요합니다. 이 컬렉션은 코드 품질 제어, 문서 일관성, 전달 운영 개선에 실제로 기여하는 스킬·연동·자동화 컴포넌트를 강조합니다. 일부 항목은 MCP 기능을 포함할 수 있지만, 페이지의 중심은 개발자 워크플로우 가이드와 실무 적용성입니다.

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, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.

P1 solution

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.

High-intent solution pages are safer recovery surfaces than broad skill detail expansion.

P1 solution

Workflow Automation Solution

A use-case page for users searching for repeatable automation patterns instead of one-off tools.

Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.

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: Killer-Skills editorial review within the recovery-focused authority queue.
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. Open the installation docs before opening more OpenCode-related repositories.
2. Choose one tool that best supports coding, review, handoff, or automation.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
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. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more projects or more teammates.
4. Document the chosen OpenCode workflow baseline after the first clean rollout.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.

Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check OpenCode workflow choices before you standardize a team stack.

sync-readme

lbb00

sync-readme는 README.md와 README_ZH.md 문서를 동기화하는 도구입니다

★ 17

⑂ 0

인공지능

update-docs

lbb00

Update all project documentation after code changes.

★ 17

⑂ 0

인공지능

lore-field-repair

lorehq

Guided workflow for diagnosing and fixing harness bugs in deployed instances

★ 16

⑂ 0

인공지능

Related Authority Collections

If This Page Is Close, Keep Narrowing With Adjacent Authority Pages

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.

P1 collection

Gemini Workflow Tools to Install First

A Gemini-specific collection that turns compatibility research into a curated install path for real delivery teams.

Gemini demand is easier to trust when it lands on a curated shortlist instead of a loose compatibility wrapper.

P1 collection

Top Claude Code Skills

A platform-specific collection for one of the clearest demand clusters in the product ecosystem.

Platform collections let the site recover with narrower, more trustworthy topical intent.

P1 collection

Agent Framework Tools to Install First

A framework and SDK collection for teams building agent foundations, not just browsing vendor names.

Framework intent strengthens the site's product judgment and reduces the mirror-site posture.

P1 collection

Python Workflow Tools to Install First

A Python engineering collection built for teams choosing installable workflow helpers instead of browsing raw packages.

Python demand converts better when the site looks like an install guide with judgment, not a bulk package mirror.

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.

이 컬렉션들은 어떤 워크플로를 위해 만들어졌나요?

워크플로 자동화, 프로세스 자동화, 문서 작업, 데이터 워크플로 및 재사용 가능한 스킬 스택을 중심으로 구성되어 있습니다.

컬렉션과 메인 스킬 디렉터리의 차이점은?

스킬 디렉터리는 직접 검색과 필터링에 적합하고, 컬렉션은 완전한 워크플로를 위한 보완적 스킬 묶음을 찾는 데 적합합니다.

이 컬렉션들을 Claude Code나 Cursor에 설치할 수 있나요?

네. 이 컬렉션의 스킬들은 일반적으로 Claude Code, Cursor, Windsurf 및 기타 지원 환경에서 통합 설치 흐름으로 작동합니다.

Additional Recovery 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.

P0 collection

Agent Workflow Building Tools

A workflow-first collection that explains why related skills belong together and what job they solve.

Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.

P2 comparison

Claude Code vs Cursor vs Windsurf

Comparison pages are one of the best ways to prove independent judgment and avoid the mirror-site posture.

Comparisons make Killer-Skills look editorial-first instead of repo-wrapper-first.