multi-cli-review-action
Multi-CLI Review Action
Version History
- v2.4: Aligned paired intake wording with coordinator-assigned letter-based
reviewer-idslots and CLI identity recorded separately insource-cli - v2.3: Repositioned the skill as a workflow-agnostic action-side pair contract and moved reviewer-count defaults out of the core contract
- v2.2: Added an explicit no-new-problems adoption gate and aligned workflow wording around regression-safe fixes
- v2.1: Tightened report intake rules, safety gates, and skill-spec alignment for the shared paired contract
Purpose
multi-cli-review-action is the action-side skill paired with multi-cli-review.
The current CLI uses it to consume reviewer reports generated by that paired skill. It is intentionally workflow-agnostic: any workflow, command pack, or manual coordinator may use it, as long as the reviewer reports follow the paired contract.
It exists to do one job safely:
More from starforall/ai-coding-toolkit
demand-risk-assessment
Use when 需要对外包/项目/需求做“接/谈判后接/暂停/拒绝”的风险与收益判断，尤其在范围/验收/付款/合规/工期/依赖不清，或出现应急插队、续约变更、多需求排序、AI/LLM 等高不确定信号时。
38multi-cli-review
Use when a reviewer CLI must analyze a skill, command, workflow, document, config, or code artifact and produce a structured defect report for the current CLI to consume, especially after requests like "分析这个 skill 的问题", "输出结构化问题报告", or "做多 CLI 审查".
37collaborating-with-claude
Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review. Supports multi-turn sessions via SESSION_ID. Optimized for low-token, file/line-based handoff.
33example-skill
Minimal example skill template compatible with the Skills CLI (`npx skills add`).
1