T09 · Insecure Skill Coding Practices
- Location
SKILL.md:173- Finding
Shell Command Injection Through Unquoted Git Branch Names
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill fits its Git branch-cleanup purpose, but it needs review because it can generate copy-paste delete commands that are unsafe for unusual branch names.
Review generated commands before running them, especially in repositories with branches created by other people. Do not paste cleanup commands blindly; branch names should be validated and shell-quoted, and remote deletions or force-deletes should be confirmed manually.
SKILL.md:173Shell Command Injection Through Unquoted Git Branch Names
The description advertises triggers such as "clean up branches," "stale branches," and especially "delete old branches," which are fairly broad natural-language phrases and could overlap with ordinary conversation about Git maintenance. The file does not provide exclusion conditions or negative examples to clarify when the skill should not activate.
Several listed triggers, including "branch cleanup," "stale branches," and "which branches can I delete," are understandable but still broad enough to match common repo discussions rather than an intentional skill invocation. The section does not define required context, exclusions, or a canonical invocation format beyond one slash-command option.