cli-providers
CLI provider capability differences across Claude, Gemini, and other providers. Use when implementing provider-specific logic, discovering CLI behavioral differences, adding new provider support, or encountering limitations where not all CLIs support the same flags.
来源信息
- 仓库
- recca0120/code-quest
- 最近来源活动
- 2026年4月19日 22:05
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 11
- 分支
- 2
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- cli-providers
- description
- CLI provider capability differences across Claude, Gemini, and other providers. Use when implementing provider-specific logic, discovering CLI behavioral differences, adding new provider support, or encountering limitations where not all CLIs support the same flags.
# CLI Provider Differences
When working on CLI integration code (spawning processes, parsing output, building args),
always consult and update the capability matrix below.
## Rules
1. **Check before assuming** — not all providers support the same flags or output formats
2. **Update on discovery** — when you find a new difference, update this file immediately
3. **Provider-agnostic by default** — shared code paths should only use universally supported features
4. **Provider-specific via config** — use the capability matrix to conditionally enable features
## Capability Matrix
See `docs/cli-providers.md` for the full matrix.
## When to Update
- A flag works on one provider but not another
- Output format differs between providers
- A new provider is added
- Stream event types differ
- Permission handling differs
## Checklist
When adding a provider-specific feature:
1. Check `docs/cli-providers.md` for current capabilities
2. Implement with provider branching if needed
3. Update the matrix with any new findings
4. Add tests covering provider-specific behavior
在 GitHub 查看