chore(github): Add write tool for markdown report#19387
Conversation
|
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| IMPORTANT: Do NOT wait for approval. | ||
| claude_args: | | ||
| --max-turns 20 --allowedTools "Bash(gh api *),Bash(gh pr list *),Bash(python3 .claude/skills/triage-issue/assets/post_linear_comment.py *),Bash(rm -f /tmp/triage_report.md)" | ||
| --max-turns 20 --allowedTools "Write(//tmp/triage_report.md),Bash(gh api *),Bash(gh pr list *),Bash(python3 .claude/skills/triage-issue/assets/post_linear_comment.py *),Bash(rm -f /tmp/triage_report.md)" |
There was a problem hiding this comment.
Double slash in Write tool path causes mismatch
High Severity
The Write tool permission path is //tmp/triage_report.md (double leading slash), but the SKILL.md instructs writing to /tmp/triage_report.md (single slash), and both the post_linear_comment.py script and the rm -f cleanup command also reference /tmp/triage_report.md. If --allowedTools does exact pattern matching, the Claude agent's attempt to write to /tmp/triage_report.md won't match the //tmp/triage_report.md permission, causing the write to be denied and the triage workflow to fail.
There was a problem hiding this comment.
This is the correct syntax: https://code.claude.com/docs/en/permissions#read-and-edit
In Claude Code's permission syntax, // is the rule prefix for "absolute path from filesystem root" — it denotes how the rule is interpreted, not the literal path string.
Codecov Results 📊Generated by Codecov Action |
size-limit report 📦
|
2 participants
Closes #19388 (added automatically)