provider-claudelisted

Track and maintain the upstream Claude Code CLI contract. Use when Anthropic ships a Claude Code release, when a `claude` flag/output/permission behaviour changes, or when an upstream scan flags drift. Process guidance only — `src/upstream-contracts.ts` is the mechanical source of truth.
verivus-oss/llm-cli-gateway · ★ 8 · AI & Automation · score 78

Install: claude install-skill verivus-oss/llm-cli-gateway

# Provider: Claude Code CLI Process guidance for keeping the gateway's Claude (`claude`) integration aligned with the upstream CLI. This skill does **not** define argv/env behaviour — the single mechanical source of truth is `UPSTREAM_CLI_CONTRACTS.claude` in `src/upstream-contracts.ts`, enforced by `validateUpstreamCliArgs` / `validateUpstreamCliEnv`. Never re-encode flags, output modes, permission modes, or session rules here or in TOML. ## Identity | Field | Value | |-------|-------| | CliType | `claude` | | Executable | `claude` | | Package | `@anthropic-ai/claude-code` (npm) | | Changelog | https://code.claude.com/docs/en/changelog.md | | Install docs | https://code.claude.com/docs/en/overview | | Watch categories | `flags`, `output-formats`, `permission-modes`, `session-resume`, `models` | These values mirror `UPSTREAM_CLI_CONTRACTS.claude.upstreamMetadata` and `docs/upstream/provider-sources.dag.toml` (`[providers.claude]`). The TypeScript metadata is authoritative; the TOML is scanner input only. ## When to use - An Anthropic Claude Code release lands and you need to check for contract drift. - A `claude` request fails the upstream contract check before spawn. - `npm run upstream:scan -- --live` reports a change on the Claude changelog. ## Scan for upstream change ```bash # Offline summary (no network): npm run upstream:scan -- --provider claude # Advisory live check against the changelog (network; manual only): npm run upstream:scan -- --live --provider claud