fix: all-in-one skill 未区分 CLI 与 MCP 使用场景,导致 CLI 禁用时误用#610
Open
fix: all-in-one skill 未区分 CLI 与 MCP 使用场景,导致 CLI 禁用时误用#610
Conversation
…ssue_mo8z9w2j_u59a3i)
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Member
Author
Attribution post-PR evaluation
Cases
|
Member
Author
|
出现了 评测的术语 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Attribution issue
Automation summary
SUMMARY:
tcbCliEnabled: false) but MCP enabled (mcpEnabled: true), the skill's guidance to "Use CLI only as a fallback when MCP tools are unavailable" was insufficient. Agents needed clearer direction that when CLI is explicitly disabled, they must use MCP tools exclusively and cannot rely on CLI batch commands like--all.config/source/skills/cloud-functions/SKILL.md(lines 118-125): Added explicit guidance to prefer MCP tools over CLI, not use CLI when explicitly disabled, and clarified that batch updates via MCP require individualmanageFunctions(action="updateFunctionConfig")calls since MCP lacks a--allparameter.config/source/skills/cloud-functions/references/operations-and-config.md(lines 156-170): Enhanced the "CLI fallback" section with stronger warnings about CLI-disabled environments and added documentation about batch update behavior differences between CLI and MCP.build-skills-repo.test.js,build-compat-config.test.js, `skill-quaChanged files
config/source/skills/cloud-functions/SKILL.mdconfig/source/skills/cloud-functions/references/operations-and-config.md