Skill execution fails when glob pattern contains backticks - shell command substitution bug
Bug Description
When running a skill (e.g., github-issue-cycle), the execution fails with a shell syntax error because backticks in glob patterns are interpreted as command substitution by bash.
Error Message
Error: Shell command failed for pattern "!`.github/PULL_REQUEST_TEMPLATE/default.md`": [stderr]
.github/PULL_REQUEST_TEMPLATE/default.md: line 2: syntax error near unexpected token `newline'
.github/PULL_REQUEST_TEMPLATE/default.md: line 2: `<!-- Briefly describe what and why you changed -->'
Root Cause
The file path .github/PULL_REQUEST_TEMPLATE/default.md is wrapped in backticks and passed to the shell. Bash interprets the backticks as command substitution, attempting to execute the markdown file as a script. The HTML comment <!-- ... --> in the markdown file then causes a bash syntax error.
Expected Behavior
File paths in glob patterns should be properly escaped before being passed to shell commands. Backticks should not trigger command substitution.
Environment
- OS: Windows 11
- Shell: bash (Git Bash)
- Claude Code version: latest
Steps to Reproduce
- Have a file at
.github/PULL_REQUEST_TEMPLATE/default.mdwith HTML comments - Run a skill that uses glob patterns (e.g.,
github-issue-cycle) - Observe shell command substitution error
Suggested Fix
Escape backticks or use single quotes when passing file paths to shell commands in the skill execution pipeline.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗