provider-claude

Solid

Track and maintain the upstream Claude Code CLI contract. Use when Anthropic ships a Claude Code release, when a `claude` flag/output/permission/subcommand behaviour changes, or when an upstream scan flags drift. Process guidance only; `src/upstream-contracts.ts` is the mechanical source of truth.

AI & Automation 16 stars 0 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
41
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 ...

Details

Author
verivus-oss
Repository
verivus-oss/llm-cli-gateway
Created
5 months ago
Last Updated
2 days ago
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category