Conversation
…d format Changed allowed-tools from JSON array syntax to official comma-separated string format per Claude Code documentation. Fixes #82 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
Claude finished @sjnims's task —— View job PR Review Complete ✓
SummaryLooks good - This is a straightforward documentation fix that corrects the What's Good✅ Correct syntax change: The PR properly converts from incorrect JSON array syntax ✅ Comprehensive fix: Both occurrences in the plugin-settings skill have been corrected:
✅ Clean markdown: Both files pass markdownlint validation with no issues. ✅ Accurate PR description: The PR clearly documents the problem, solution, and affected files with specific line numbers. ✅ Proper issue linkage: Fixes #82 is correctly referenced. Checklist Verification
RecommendationApprove and merge - This PR addresses a documentation bug with the correct fix. No changes needed. |
claude
Bot
added
documentation
1 participant
Summary
Fix
allowed-toolsfrontmatter syntax in the plugin-settings skill to use the official comma-separated string format instead of JSON array syntax.Problem
Fixes #82
The
allowed-toolsfield in two files used incorrect JSON array syntax["Tool1", "Tool2"]instead of the official comma-separated formatTool1, Tool2per Claude Code documentation.Solution
Changed the syntax in both files to match official documentation:
SKILL.md:105allowed-tools: ["Read", "Bash"]allowed-tools: Read, Bashexamples/create-settings-command.md:3allowed-tools: ["Write", "AskUserQuestion"]allowed-tools: Write, AskUserQuestionAlternatives Considered
None - the fix is unambiguous and directly specified by official Claude Code documentation.
Changes
plugins/plugin-dev/skills/plugin-settings/SKILL.md: Fixedallowed-toolssyntax on line 105plugins/plugin-dev/skills/plugin-settings/examples/create-settings-command.md: Fixedallowed-toolssyntax on line 3Testing
🤖 Generated with Claude Code