MoonBoi9001/land-pr
skills/land-pr/SKILL.md
Merge the current PR (squash by default, or rebase if specified), delete the branch, checkout main, fetch and pull. Use when the user says "land", "land the PR", "merge the PR", "merge and clean up", "land it", or wants to finish/complete a PR.
$ install --global
skillsauthnpx skillsauth add MoonBoi9001/claude-code-cli-tools land-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 5, 2026, 2:54 AM129.3s1 file scanned
SKILL.md
- name:
- land-pr
- description:
- Merge the current PR (squash by default, or rebase if specified), delete the branch, checkout main, fetch and pull. Use when the user says "land", "land the PR", "merge the PR", "merge and clean up", "land it", or wants to finish/complete a PR.
- argument-hint:
- [squash|rebase]
- allowed-tools:
- Bash
Merge the current branch's PR, clean up, and return to the base branch.
Merge strategy
Use <arg1> if provided. If not, default to --squash. Valid values: squash, rebase.
Steps
-
Check CI status on the PR:
gh pr checksInspect the exit code:
- 0 — all checks passed. Continue.
- 8 — checks are still pending. Warn the user that CI hasn't finished and stop. Don't merge on top of incomplete CI.
- any other non-zero — one or more checks failed. Report which ones and stop.
If the repo has no CI configured,
gh pr checksexits 0 with no output — treat that as "nothing to check" and continue. -
Capture the head and base branches before merging:
gh pr view --json headRefName,baseRefName -
Merge the PR — without
--delete-branch:gh pr merge --<strategy>The repo has
delete_branch_on_mergeenabled at the GitHub level, so GitHub deletes the remote head branch and auto-retargets any chained PRs onto the base branch. Passing--delete-branchwould instead close those chained PRs, so we deliberately omit it. -
Switch to the base branch, pull, and delete the local head branch:
git checkout <base> git pull git branch -D <head>Use
-D(force) — after a squash or rebase merge, the local branch tip won't match the new commit on base, so-dwould refuse. -
Prune stale remote-tracking references:
git fetch --pruneCleans up the orphaned
origin/<head>ref left behind by GitHub's remote deletion.
If any step fails, stop and report the error rather than continuing.
Related Skills
MoonBoi9001/deep-review
development
VerifiedTrustedCommunity
Run a deep multi-agent review of a GitHub PR — 6 specialized agents covering architecture, correctness, security, tests, code quality, and integration. ONLY trigger when the user's message contains the explicit phrase 'deep review' (e.g. 'deep review this PR', 'deep review PR #1234', 'do a deep review of 1234', '/deep-review'). Do NOT trigger on bare 'review', 'review this', 'review the PR', 'code review', 'what do you think of this PR', or pasted PR URLs without 'deep review' in the message — those are handled by the lighter /review skill. The literal phrase 'deep review' must appear in the user's message; absence of that phrase means do not invoke this skill.
4SKILL.mdUpdated May 12, 2026
MoonBoi9001/skills/re-explain
data-ai
VerifiedTrustedCommunity
--- name: re-explain description: Re-explain a concept from the ground up when an earlier explanation didn't land. Trigger aggressively whenever the user signals confusion about recent technical content — phrases like "i don't get it", "from scratch", "ground up", "explain again", "this makes no sense", "try again", "you need to work better", "what's X" (where X was something just mentioned), or invoking /re-explain directly. Also trigger on quieter cues like the user re-quoting a phrase from th
4SKILL.mdUpdated May 5, 2026
MoonBoi9001/load-prior-session
development
VerifiedTrustedCommunity
Load a high-fidelity recap of a prior Claude Code session into the current session's context. The goal is to be LESS lossy than running /compact would be — the user is invoking this skill precisely because /compact discards detail they need. Use this when the user wants to "resume", "pick up", "continue", or "load context from" a previous session — especially a long one (hundreds of thousands of tokens) where actually resuming the session would be prohibitively expensive, or where the session was auto-compacted mid-flow and a lot of detailed work happened after the last compaction that another /compact pass would crush. Also trigger on phrases like "recap the last session", "what was I working on yesterday", "load the prior chat", or "/load-prior-session". The skill extracts via a subagent so the full transcript never enters the current session's context.
4SKILL.mdUpdated May 5, 2026
MoonBoi9001/review-todo
development
VerifiedTrustedCommunity
Convert the most recent code review in the conversation into a grouped numbered checklist (Decisions needed / Fixes / Polish) of issues to fix. Use this skill whenever the user wants to extract, list, summarize, or triage the issues a reviewer raised — including phrasings like "list the issues from that review", "make me a todo from the review", "turn the review into a checklist", "what did the review flag", "summarize that review as a list", "give me every nit from above", or "/review-todo". Trigger especially as a natural follow-up to /review, /deep-review, /security-review, /ultrareview, or any pasted PR / inline review the user wants to act on. The output is a numbered list of every concrete issue the review raised, grouped under bold section headings, with file:line references appended in parentheses, and decision items rendered with a `→` arrow callout below the description posing the specific question — and lettered choices below that when the reviewer named discrete alternatives.
4SKILL.mdUpdated Apr 30, 2026