fix(cli): use valid allowed-tools syntax in checkly skill frontmatter [ship] - #1433
Merged
Conversation
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.
Affected Components
Notes for the Reviewer
The
allowed-toolsfrontmatter in the public checkly skill was invalid on two counts: entries must be comma-separated, and Bash permission rules use spaces between command words, not colons. As written,Bash(npx:checkly:*)only matches a literal command starting withnpx:checkly:, which never occurs, so the intended pre-approval did nothing.Fixed to:
Changed in the source (
packages/cli/src/ai-context/skill.md) and regenerated the published copy atskills/checkly/SKILL.mdviapnpm --filter checkly run prepare+pnpm run sync:skills.