toss-invest-sdk: Skill for Claude Code

Toss API update and release

Run this workflow from the root of the toss-invest-sdk repository. An explicit invocation requesting this release authorizes the release commit, version tag, and normal push that triggers GitHub Actions. A request to check or prepare only does not authorize those actions. Never force-push, amend, reset, overwrite tags, include unrelated work, or publish directly as a workaround.

1. Check the repository and upstream

1. Read applicable repository instructions. Inspect git status -sb, the current branch, recent commits, the remote, packages/sdk/openapi-ts.config.ts, packages/sdk/src/generated/spec.json, and .github/workflows/publish.yml. Fetch the remote branch and tags without changing the working tree. If there are staged or unstaged changes, an unexpected branch, local/remote divergence, or unrelated unpushed commits, stop before modifying or pushing and explain what needs resolution; never rewrite the user's work.
2. Download the configured official latest/openapi.json to a temporary file. Compare its info.version, paths, operations, and schemas with the saved spec. Compare versions as semver. If the official version is not greater, do not create a release. If the content changed despite the same version, report the difference and ask how to proceed. If the version is invalid, lower, or the download fails, report the problem instead of guessing.

2. Update the SDK and MCP

1. Run pnpm generate. Confirm the saved generated spec matches the downloaded snapshot as parsed JSON. If upstream changed during generation, recheck before continuing; never silently release an inconsistent snapshot. Review the spec and generated diff for added, removed, and changed endpoints and request/response schemas.
2. Inspect affected callers, apps/mcp/src/server.ts, generated request schemas, tests, exports, and docs. Adapt existing MCP tools to changed API contracts. Expose new applicable REST operations as MCP tools using existing SDK and Zod patterns, descriptions, and annotations. Account calls must use the selected account header. New trading mutations must retain the existing opt-in and order safety rules. Do not silently expose mutations as read-only. If a safe mapping is unclear, stop and explain rather than inventing behavior.
3. Update relevant tests and apps/mcp/README.md. Check request serialization, validation, and pagination when applicable. Add focused tests for new behavior and compatibility; do not test only generated implementation details.