sonht1109/gh-clone-pr
.opencode/skills/gh-clone-pr/SKILL.md
Use when user asks to clone a GitHub Pull Request locally using the GitHub CLI.
tools
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add sonht1109/vscode-copilot-kit gh-clone-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 17, 2026, 1:47 AM14.2s2 files scanned
SKILL.md
- name:
- gh-clone-pr
- description:
- Use when user asks to clone a GitHub Pull Request locally using the GitHub CLI.
GitHub Clone PR Skill
Use this skill when the user requests to clone a GitHub Pull Request (PR) locally using the GitHub CLI (gh command).
Notes
- cwd: The current working directory of the local repository where the user is running the commands (not
.opencodedirectory). Must use this cwd for all file paths in the steps below.
Steps
Must follow these steps strictly in order:
- Extract PR Information: Identify the repository owner, repository name, and PR number from the user's request.
<OWNER>is the GitHub repository owner.<REPO>is the GitHub repository name.<PR_NUMBER>is the number of the Pull Request.
- Get PR description: Use the GitHub CLI to fetch the PR details to ensure it exists and gather necessary information and save into
notes/prs/<PR_NUMBER>/details.json.
First, create the directory for the PR if it doesn't exist:
mkdir -p <cwd>/notes/prs/<PR_NUMBER>
Then run command:
gh pr view <PR_NUMBER> --repo <OWNER>/<REPO> --json title,body > <cwd>/notes/prs/<PR_NUMBER>/details.json
- Clone the PR: Use the GitHub CLI to clone the PR locally into
<cwd>/notes/prs/<PR_NUMBER>. Run command:
gh pr diff <PR_NUMBER> --repo <OWNER>/<REPO> > <cwd>/notes/prs/<PR_NUMBER>/diff.patch
- Separate patch file: separate patch files for the PR diff into multiple files to keep changes organized. Run script:
node <cwd>/.opencode/skills/gh-clone-pr/scripts/separate-patch.js <PR_NUMBER>
- Provide confirmation: Inform the user that the PR has been successfully cloned and provide the local path to the cloned PR. Provide output following the specified format.
Output Format
Provide output in the following format:
The GitHub Pull Request has been successfully cloned.
- PR description: `<cwd>/notes/prs/<PR_NUMBER>/details.json`
- PR diff patch dir: `<cwd>/notes/prs/<PR_NUMBER>/contents`
Notes
- Stop and inform user if there are any errors during the process, especially when running the separate patch script.
Related Skills
sonht1109/test-writing
development
VerifiedTrustedCommunity
This skill focuses on writing/designing effective and comprehensive tests for code. It emphasizes the importance of covering various scenarios, including happy cases, error cases, edge cases, and input validation. The skill also highlights the need to write tests based on expected correct behavior rather than current implementation, and to maintain a high level of coverage (at least 80%).
SKILL.mdUpdated Apr 17, 2026
sonht1109/sequential-thinking
content-media
VerifiedTrustedCommunity
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope. DO NOT use when single-step answers suffice.
SKILL.mdUpdated Apr 17, 2026
sonht1109/.opencode/skills/sentry
tools
VerifiedTrustedCommunity
--- name: sentry description: Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI. Primary workflow: given a short issue ID (e.g. PROJECT-123), fetch full bug report with description and stack trace. --- # Sentry CLI Skill This skill handles Sentry CLI operations: authentication, issue lookup by short ID, event details, and bug report g
SKILL.mdUpdated Apr 17, 2026
sonht1109/markdown
documentation
VerifiedTrustedCommunity
Use when doing tasks related to markdown files, such as editing README.md or other documentation files.
SKILL.mdUpdated Apr 17, 2026