timtoronto634/merge-pr
.claude/skills/merge-pr/SKILL.md
Merge a GitHub pull request by number using squash merge
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add timtoronto634/timtoronto634.github.io merge-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: Apr 16, 2026, 2:36 PM14.3s1 file scanned
SKILL.md
- name:
- merge-pr
- description:
- Merge a GitHub pull request by number using squash merge
- argument-hint:
- [pr-number]
- allowed-tools:
- Bash(gh *, git *)
Merge a GitHub pull request.
- If
$ARGUMENTSis provided, use it as the PR number. Otherwise, rungh pr view --json numberto get the PR for the current branch. - Run
gh pr view <number> --json title,state,mergeableto verify the PR is open and mergeable - If the PR is not mergeable, inform the user and stop
- Merge using
gh pr merge <number> --squash - Run
git checkout master && git pull --pruneto update local master and clean up stale remote-tracking branches - Report the result to the user
Related Skills
timtoronto634/create-pr
testing
VerifiedTrustedCommunity
Create a GitHub pull request from the current branch with a summary and test plan
SKILL.mdUpdated Apr 16, 2026
timtoronto634/commit-staged
tools
VerifiedTrustedCommunity
Commit currently staged changes with a conventional commit message
SKILL.mdUpdated Apr 16, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026