opencode-sdk

Regenerate OpenCode SDKs after server or API contract changes.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill opencode-sdk-open-hax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-sdk
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/opencode-sdk
Command: npx skills add https://github.com/open-hax/opencode-skills --skill opencode-sdk-open-hax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode SDKs and client contracts often drift when server endpoints or API contracts change. This Skill provides a structured workflow to regenerate the SDK code and examples to align with the latest server definitions.

Core Features & Use Cases

  • Regenerate SDKs under packages/sdk/* when server contracts change.
  • Validate regenerated SDKs against the OpenCode SDK docs and example usage.
  • Synchronize accompanying docs and samples to prevent integration regressions.

Quick Start

Run the regeneration workflow whenever server contracts are updated to refresh all affected SDK packages and verify consistency with the docs.

Frequently Asked Questions about opencode-sdk

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

FAQPage Schema
How do I regenerate SDKs after server contract changes?

You can regenerate SDKs after server contract changes by running a structured workflow that targets packages/sdk/*, updating the code and examples to align with the latest server definitions.

Why does my client SDK drift from server endpoints?

Client SDKs drift from server endpoints when API contracts or server definitions change without synchronizing the SDK code. Regeneration ensures the SDK reflects the latest server updates.

How do I validate regenerated SDKs against OpenCode SDK docs?

You validate regenerated SDKs against OpenCode SDK docs by applying the regeneration workflow, which verifies that artifacts meet documentation standards and updates sample usages for consistency.

Can I update sample usages when API contracts change?

Yes, you can update sample usages by regenerating the SDK packages, which synchronizes accompanying docs and samples to prevent integration regressions after API contract changes.

When do I need to regenerate my SDK code?

You need to regenerate your SDK code whenever server contracts are updated or endpoints change. This refreshes all affected SDK packages and verifies consistency with the documentation.

What is the best way to prevent integration regressions in SDK packages?

The best way to prevent integration regressions is to regenerate SDKs after server changes, validate the artifacts against documentation standards, and update sample usages accordingly.