Verify a merged PR actually landed correctly in this repo and clean up after it. Use right after a PR merges (especially with auto-merge) to confirm the merge commit, or for older PRs the squashed commit, matches your branch by content, catch late commits that were orphaned by the auto-merge race, and post its review record and update memory.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
Step 4 authorizes state-changing git operations (worktree removal, remote branch deletion, and `git branch -D`) on a shared hosted repository, but no supplied text establishes irreversible operational loss, so the tier is low.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required workflow reads GitHub PR state and comments through `gh pr view` and checks whether the PR's comments already hold a `Review record`, which is a GitHub PR reading path where outsiders can post comments.
BigSimmo/PsychSift
fada614
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.