Security audit
Security checks for vulnerabilities and agentic risk
The skill is purpose-aligned for finishing a Git branch, but its inconsistent worktree cleanup instructions could cause a user's worktree to be deleted unexpectedly after creating a PR.
Review the cleanup behavior before installing. This skill is not trying to exfiltrate data or install persistence, but it should be corrected so PR creation clearly preserves the worktree unless the user explicitly asks to remove it, and any worktree deletion should require confirmation and a clean-worktree check.
The skill instructs git worktree remove <worktree-path> with no warning that this removes the linked working directory from the filesystem and may fail or behave destructively depending on local state. In a branch-finishing workflow, users may still expect the worktree directory to remain available after merge/PR steps, so silent removal creates risk of data loss or confusion.
The skill gives conflicting instructions for Option 2: Step 5 says to clean up the worktree for Options 1, 2, and 4, while the Quick Reference says Option 2 should keep the worktree. In an automation context, contradictory destructive guidance can cause unintended removal of a developer's worktree, disrupting ongoing work and potentially deleting uncommitted filesystem contents in that worktree.
The 'Common Mistakes' and 'Always' sections instruct cleanup only for Options 1 and 4, which contradicts Step 5's directive to also clean up for Option 2. This inconsistency increases the chance that an agent will choose the more destructive interpretation and remove a worktree after pushing a PR, even though the surrounding guidance implies it should be preserved.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **Problem:** Remove worktree when might need it (Option 2, 3)
- **Fix:** Only cleanup for Options 1 and 4
**No confirmation for discard**
- **Problem:** Accidentally delete work
- **Fix:** Require typed "discard" confirmation
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
**Never:**
- Proceed with failing tests
- Merge without verifying tests on result
- Delete work without confirmation
- Force-push without explicit request
**Always:**
No suspicious patterns detected.