Extract Repo
archibate/dotfiles-opencode
Download GitHub repos as clean source code (no .git history) to WORKDIR.
Complete GitHub operations via gh CLI - repos, issues, PRs, code search, releases, file management When user mentions GitHub, repositories, issues, PRs, gh command, code search, commits, file contents
$ npx skills add shepherdjerred/monorepo --skill gh-helper -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shepherdjerred/monorepo gh-helper --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/dotfiles/dot_agents/skills/gh-helper .claude/skills/gh-helper && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gh-helper" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_agents/skills/gh-helper into .claude/skills/gh-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-helper", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_agents/skills/gh-helperType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shepherdjerred/monorepo --skill gh-helper -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shepherdjerred/monorepo gh-helper --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/dotfiles/dot_agents/skills/gh-helper .agents/skills/gh-helper && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gh-helper" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_agents/skills/gh-helper into .agents/skills/gh-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-helper", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shepherdjerred/monorepo --skill gh-helper -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shepherdjerred/monorepo gh-helper --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/dotfiles/dot_agents/skills/gh-helper .cursor/skills/gh-helper && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gh-helper" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_agents/skills/gh-helper into .cursor/skills/gh-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-helper", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shepherdjerred/monorepo.git --path packages/dotfiles/dot_agents/skills/gh-helper--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shepherdjerred/monorepo --skill gh-helper -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shepherdjerred/monorepo gh-helper --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/dotfiles/dot_agents/skills/gh-helper .gemini/skills/gh-helper && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gh-helper" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_agents/skills/gh-helper into .gemini/skills/gh-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-helper", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shepherdjerred/monorepo gh-helperInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shepherdjerred/monorepo --skill gh-helper -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/dotfiles/dot_agents/skills/gh-helper .github/skills/gh-helper && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gh-helper" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_agents/skills/gh-helper into .github/skills/gh-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-helper", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shepherdjerred/monorepo --skill gh-helper -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shepherdjerred/monorepo gh-helper --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/dotfiles/dot_agents/skills/gh-helper .opencode/skills/gh-helper && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gh-helper" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_agents/skills/gh-helper into .opencode/skills/gh-helper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-helper", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
gh-helperComplete GitHub operations via gh CLI - repos, issues, PRs, code search, releases, file management When user mentions GitHub, repositories, issues, PRs, gh command, code search, commits, file contents
Gh Helper is an agent skill from shepherdjerred/monorepo. Complete GitHub operations via gh CLI - repos, issues, PRs, code search, releases, file management When user mentions GitHub, repositories, issues, PRs, gh command, code search, commits, file contents
Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/actions-releases-api.md`, `references/issue-operations.md` and `references/pr-operations.md`).
It sits in Development, covering Codebase onboarding, File organization and Monorepo tooling. It works with GitHub. The repository describes itself as: Monorepo for all of my projects. The licence is GPL-3.0.
Read from SKILL.md and the folder at commit da14ae9. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghgitjqFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Gh Helper loads about 4.4k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 529 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from shepherdjerred/monorepo at commit da14ae9, republished under its GPL-3.0 licence (© shepherdjerred). 529 words, ~4,363 tokens.
.claude/skills/gh-helper/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Complete GitHub operations via gh CLI and GitHub API. This skill replaces GitHub MCP server functionality, providing CLI/API equivalents for all operations.
In shepherdjerred/monorepo, monorepo-delivery is authoritative for every
feature branch and PR. Use toolkit gh here for inspection, review comments,
and other explicitly requested GitHub operations; it supplies this repository
as the default and otherwise preserves native CLI behavior. Do not create
branches, create feature PRs, or merge them with the generic gh examples
below. Load monorepo-delivery before any branch or feature-PR mutation.
This monorepo uses Woodpecker CI, not GitHub Actions. Use
toolkit ci wait for merge readiness, toolkit ci explain for blockers, and
toolkit woodpecker for native CI operations. The generic Actions examples later in this skill
apply only to repositories that actually use GitHub Actions.
| MCP Tool | CLI/API Equivalent |
|---|---|
create_or_update_file | gh api -X PUT /repos/{owner}/{repo}/contents/{path} |
search_repositories | gh search repos <query> |
create_repository | gh repo create <name> |
get_file_contents | gh api /repos/{owner}/{repo}/contents/{path} |
push_files | git add && git commit && git push |
create_issue | gh issue create |
create_pull_request | gh pr create |
fork_repository | gh repo fork |
create_branch | gh api -X POST /repos/{owner}/{repo}/git/refs |
list_commits | gh api /repos/{owner}/{repo}/commits |
list_issues | gh issue list |
update_issue | gh issue edit |
add_issue_comment | gh issue comment |
search_code | gh search code <query> |
search_issues | gh search issues <query> |
search_users | gh api /search/users?q=<query> |
get_issue | gh issue view <number> |
get_pull_request | gh pr view <number> |
list_pull_requests | gh pr list |
create_pull_request_review | gh pr review |
merge_pull_request | gh pr merge |
get_pull_request_files | gh api /repos/{owner}/{repo}/pulls/{number}/files |
get_pull_request_status | gh pr checks |
update_pull_request_branch | gh api -X PUT /repos/{owner}/{repo}/pulls/{number}/update-branch |
get_pull_request_comments | gh api /repos/{owner}/{repo}/pulls/{number}/comments |
get_pull_request_reviews | gh api /repos/{owner}/{repo}/pulls/{number}/reviews |
Safe read-only commands:
gh repo view, gh repo listgh issue list, gh issue viewgh pr list, gh pr view, gh pr diff, gh pr checksgh release list, gh release viewgh search repos, gh search code, gh search issuesgh status# Basic search
gh search repos "kubernetes operator"
# With filters
gh search repos "react" --language typescript --stars ">1000"
gh search repos "cli tool" --owner hashicorp
gh search repos "mcp server" --topic model-context-protocol
# JSON output for parsing
gh search repos "query" --json fullName,description,stargazersCount# Interactive creation
gh repo create
# Create with options
gh repo create my-repo --public --description "My project"
gh repo create my-repo --private --clone
# Create from template
gh repo create my-repo --template owner/template-repo
# Create org repo
gh repo create my-org/my-repo --public# Fork to your account
gh repo fork owner/repo
# Fork and clone
gh repo fork owner/repo --clone
# Fork to organization
gh repo fork owner/repo --org my-org
# Fork with custom name
gh repo fork owner/repo --fork-name my-fork# Get file content via API (returns base64)
gh api /repos/{owner}/{repo}/contents/{path} | jq -r '.content' | base64 -d
# Get file from specific branch
gh api /repos/{owner}/{repo}/contents/{path}?ref=branch-name
# Get directory listing
gh api /repos/{owner}/{repo}/contents/{path}
# Get raw file content
gh api /repos/{owner}/{repo}/contents/{path} -H "Accept: application/vnd.github.raw"# Create new file
gh api -X PUT /repos/{owner}/{repo}/contents/{path} \
-f message="Add new file" \
-f content="$(echo 'file content' | base64)" \
-f branch="main"
# Update existing file (requires SHA)
SHA=$(gh api /repos/{owner}/{repo}/contents/{path} | jq -r '.sha')
gh api -X PUT /repos/{owner}/{repo}/contents/{path} \
-f message="Update file" \
-f content="$(echo 'new content' | base64)" \
-f sha="$SHA" \
-f branch="main"Use git commands for pushing multiple files:
# Stage and commit multiple files
git add file1.txt file2.txt
git commit -m "Add multiple files"
git push origin branch-name
# Or use a single commit for all changes
git add .
git commit -m "Update files"
git push# Via git (local)
git checkout -b new-branch
git push -u origin new-branch
# Via API (remote, from default branch)
SHA=$(gh api /repos/{owner}/{repo}/git/refs/heads/main | jq -r '.object.sha')
gh api -X POST /repos/{owner}/{repo}/git/refs \
-f ref="refs/heads/new-branch" \
-f sha="$SHA"
# From specific branch
SHA=$(gh api /repos/{owner}/{repo}/git/refs/heads/source-branch | jq -r '.object.sha')
gh api -X POST /repos/{owner}/{repo}/git/refs \
-f ref="refs/heads/new-branch" \
-f sha="$SHA"# List commits via CLI
git log --oneline -20
# List commits via API
gh api /repos/{owner}/{repo}/commits
# With filters
gh api "/repos/{owner}/{repo}/commits?sha=branch&per_page=10"
gh api "/repos/{owner}/{repo}/commits?author=username"
gh api "/repos/{owner}/{repo}/commits?since=2024-01-01T00:00:00Z"
# JSON output
gh api /repos/{owner}/{repo}/commits --jq '.[].commit.message'# List open issues
gh issue list
# With filters
gh issue list --state open
gh issue list --state closed
gh issue list --state all
gh issue list --assignee @me
gh issue list --assignee username
gh issue list --author @me
gh issue list --label bug
gh issue list --label "bug,priority:high"
gh issue list --milestone "v1.0"
# Search with query
gh issue list --search "is:open label:bug"
# JSON output
gh issue list --json number,title,state,labels# View issue
gh issue view 123
# View in web browser
gh issue view 123 --web
# JSON output
gh issue view 123 --json number,title,body,state,labels,assignees,comments
# Get comments
gh issue view 123 --comments# Interactive
gh issue create
# With options
gh issue create --title "Bug report" --body "Description"
gh issue create --title "Feature" --label enhancement --assignee @me
gh issue create --title "Bug" --milestone "v1.0" --project "Board"
# From file
gh issue create --title "Issue" --body-file issue-body.md
# Open in editor
gh issue create --title "Issue" --editor# Edit title
gh issue edit 123 --title "New title"
# Edit body
gh issue edit 123 --body "New description"
gh issue edit 123 --body-file updated.md
# Modify labels
gh issue edit 123 --add-label "priority:high"
gh issue edit 123 --remove-label "needs-triage"
# Modify assignees
gh issue edit 123 --add-assignee username
gh issue edit 123 --remove-assignee username
# Change milestone
gh issue edit 123 --milestone "v2.0"
# Close/reopen
gh issue close 123
gh issue reopen 123# Add comment
gh issue comment 123 --body "This is a comment"
# From file
gh issue comment 123 --body-file comment.md
# Open in editor
gh issue comment 123 --editor
# Edit last comment
gh issue comment 123 --edit-last --body "Updated comment"# Basic search
gh search issues "memory leak"
# With filters
gh search issues "bug" --repo owner/repo
gh search issues "type:bug" --state open
gh search issues "label:critical" --assignee username
gh search issues "is:pr is:merged" --author username
# JSON output
gh search issues "query" --json number,title,repository,state# List open PRs
gh pr list
# With filters
gh pr list --state open
gh pr list --state closed
gh pr list --state merged
gh pr list --state all
gh pr list --author @me
gh pr list --assignee username
gh pr list --label "needs-review"
gh pr list --base main
gh pr list --head feature-branch
# Search with query
gh pr list --search "is:open review:required"
# JSON output
gh pr list --json number,title,state,author,labels# View PR
gh pr view 123
# View in web
gh pr view 123 --web
# JSON output
gh pr view 123 --json number,title,body,state,author,labels,reviews,commits,files
# View comments
gh pr view 123 --commentsFor shepherdjerred/monorepo, use git-spice branch submit or
git-spice stack submit instead. The commands below are for repositories that
do not use git-spice.
# Interactive
gh pr create
# With options
gh pr create --title "Fix bug" --body "Description"
gh pr create --title "Feature" --base main --head feature-branch
gh pr create --fill # Use commit info
gh pr create --draft # Create as draft
# With reviewers
gh pr create --title "PR" --reviewer user1,user2
gh pr create --title "PR" --reviewer team:my-team
# With labels and assignees
gh pr create --title "PR" --label bug --assignee @me
# Open in web to finish
gh pr create --web# View diff
gh pr diff 123
# Via API (detailed file info)
gh api /repos/{owner}/{repo}/pulls/123/files
# JSON with additions/deletions
gh api /repos/{owner}/{repo}/pulls/123/files --jq '.[] | {filename, status, additions, deletions}'# View checks
gh pr checks 123
# Watch checks in real-time
gh pr checks 123 --watch
# Wait for checks to complete
gh pr checks 123 --watch --fail-level all
# JSON output
gh pr checks 123 --json name,state,conclusion# Approve
gh pr review 123 --approve
# Request changes
gh pr review 123 --request-changes --body "Please fix the tests"
# Comment only
gh pr review 123 --comment --body "Looks good so far"
# Add inline comments via API
gh api -X POST /repos/{owner}/{repo}/pulls/123/reviews \
-f body="Review comment" \
-f event="COMMENT" \
-f comments='[{"path":"file.js","position":10,"body":"Consider refactoring"}]'# Via API
gh api /repos/{owner}/{repo}/pulls/123/reviews
# Get review details
gh api /repos/{owner}/{repo}/pulls/123/reviews --jq '.[] | {user: .user.login, state: .state, body: .body}'# Review comments (inline)
gh api /repos/{owner}/{repo}/pulls/123/comments
# Issue comments (general)
gh api /repos/{owner}/{repo}/issues/123/comments
# All comments with details
gh api /repos/{owner}/{repo}/pulls/123/comments --jq '.[] | {user: .user.login, body: .body, path: .path}'For shepherdjerred/monorepo, merging is handled through the repository's
approved git-spice workflow and explicit human/operator action. Do not use
these generic commands for feature work in this repository.
# Merge (default method)
gh pr merge 123
# Squash merge
gh pr merge 123 --squash
# Rebase merge
gh pr merge 123 --rebase
# Delete branch after merge
gh pr merge 123 --delete-branch
# Auto-merge when checks pass
gh pr merge 123 --auto --squash
# With custom commit message
gh pr merge 123 --squash --subject "feat: Add feature" --body "Detailed description"# Via API
gh api -X PUT /repos/{owner}/{repo}/pulls/123/update-branch \
-f expected_head_sha="current-head-sha"
# Or use git locally
gh pr checkout 123
git merge main
git push# Basic search
gh search code "function authenticate"
# In specific repo
gh search code "TODO" --repo owner/repo
# With language filter
gh search code "interface User" --language typescript
# With path filter
gh search code "config" --filename "*.yaml"
# JSON output
gh search code "query" --json path,repository,textMatches# Via API
gh api "/search/users?q=fullname:John+type:user"
# With filters
gh api "/search/users?q=location:Seattle+followers:>100"
# Search by email domain
gh api "/search/users?q=email:@company.com"gh release list
gh release list --limit 10gh release view v1.0.0
gh release view latest# Create release
gh release create v1.0.0
# With options
gh release create v1.0.0 --title "Version 1.0.0" --notes "Release notes"
gh release create v1.0.0 --generate-notes
gh release create v1.0.0 --draft
gh release create v1.0.0 --prerelease
# Upload assets
gh release create v1.0.0 ./dist/*.tar.gz# Login (interactive)
gh auth login
# With clipboard (OAuth code auto-copied)
gh auth login --clipboard
# Check status
gh auth status
# Switch accounts
gh auth switch
# Logout
gh auth logout# Set editor
gh config set editor "code --wait"
gh config set editor vim
# Create aliases
gh alias set prs 'pr list --author @me'
gh alias set co 'pr checkout'
gh alias set issues 'issue list --assignee @me'
# List aliases
gh alias list# Open repo in browser
gh browse
# Open specific PR
gh browse 123
# Open issues page
gh browse -- issues
# Open settings
gh browse -- settings
# Open file
gh browse -- src/main.tsFor any operation not covered by gh commands:
# GET request
gh api /repos/{owner}/{repo}/issues
# POST request
gh api -X POST /repos/{owner}/{repo}/issues \
-f title="New issue" \
-f body="Description"
# PUT request
gh api -X PUT /repos/{owner}/{repo}/issues/123 \
-f state="closed"
# DELETE request
gh api -X DELETE /repos/{owner}/{repo}/issues/comments/456
# With pagination
gh api /repos/{owner}/{repo}/issues --paginate
# JSON parsing with jq
gh api /repos/{owner}/{repo}/issues --jq '.[].title'
# GraphQL queries
gh api graphql -f query='
query {
repository(owner: "owner", name: "repo") {
issues(first: 10) {
nodes { title number }
}
}
}
'# Create branch and make changes
git checkout -b feature/new-thing
# ... make changes ...
git add path/to/changed-file && git commit -m "Add new feature"
git push -u origin feature/new-thing
# Create PR
gh pr create --fill
# Check status and merge
gh pr checks --watch
gh pr merge --squash --delete-branch# PRs waiting for your review
gh pr list --search "review-requested:@me"
# Your open PRs
gh pr list --author @me
# Check PR status
gh pr checks --watch# Create and push tag
git tag v1.0.0
git push origin v1.0.0
# Create release with auto-generated notes
gh release create v1.0.0 --generate-notes
# Upload release assets
gh release upload v1.0.0 ./dist/*.tar.gzAsk the user for clarification when:
© shepherdjerred, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in packages/dotfiles/dot_agents/skills/gh-helper of shepherdjerred/monorepo.
Open the folder on GitHubat commit da14ae9
Gh Helper next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gh Helper this skillshepherdjerred/monorepo | 112 | — | ~4.4k | Automated safety check: Pass | GPL-3.0 | |
| Extract Repoarchibate/dotfiles-opencode | 108 | 1 repos | ~370 | Automated safety check: Pass | None | |
| Subtree Publishcat-xierluo/legal-skills | 713 | — | ~1.8k | Automated safety check: Notes | MIT | |
| Git Project Statusespennilsen/pi | 122 | — | ~4.4k | Automated safety check: Notes | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 55k | — | ~3.8k | Automated safety check: Pass | MIT |
archibate/dotfiles-opencode
Download GitHub repos as clean source code (no .git history) to WORKDIR.
cat-xierluo/legal-skills
将 monorepo 中的子目录通过 git subtree 推送到独立 GitHub 仓库。支持注册清单、变更自动检测、增量推送。本技能应在用户提交涉及已注册子项目的变更后,或手动请求推送到独立仓库时使用。不要用于初次创建 monorepo 或管理 git submodule。
espennilsen/pi
Generate comprehensive status reports for git repositories. An agent skill from espennilsen/pi.
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
shepherdjerred/monorepo
Bun runtime APIs and current operational patterns for files, processes, modules, networking, databases, tests, and deployment.
shepherdjerred/monorepo
Current Bun test runner guidance for discovery, isolation, parallelism, sharding, changed tests, mocks, timers, snapshots, coverage, DOM Testing Library, and integration teardown.
shepherdjerred/monorepo
Current Bun workspace guidance for isolated and hoisted linkers, catalogs, filters, scripts, dependency classes, lockfiles, lifecycle trust, caches, publishing, TypeScript package exports, and…
shepherdjerred/monorepo
This skill should be used when the user asks to "deep research", "research this topic", "investigate thoroughly", "do a deep dive on", "comprehensive research on", "find everything about", "survey…
shepherdjerred/monorepo
This skill should be used when the user asks to "create a Figma design", "design in Figma", "make a Figma mockup", "create an app icon", "design UI", "render JSX to Figma", "export from Figma"…
shepherdjerred/monorepo
Current Fish shell scripting, functions, abbreviations, completions, variables, events, configuration, plugins, testing, and safety guidance.
Works with
Categories
Complete GitHub operations via gh CLI - repos, issues, PRs, code search, releases, file management When user mentions GitHub, repositories, issues, PRs, gh command, code search, commits, file contents. Gh Helper is an agent skill from shepherdjerred/monorepo.
Gh Helper fits situations like: mentions GitHub; tasks that involve Codebase onboarding; tasks that involve File organization.
Run `npx skills add shepherdjerred/monorepo --skill gh-helper -a claude-code`. Or copy the skill folder (packages/dotfiles/dot_agents/skills/gh-helper in shepherdjerred/monorepo) into .claude/skills/gh-helper in your project. Claude Code loads it when a task matches its description.
Run `npx skills add shepherdjerred/monorepo --skill gh-helper -a codex`. Or copy the skill folder (packages/dotfiles/dot_agents/skills/gh-helper in shepherdjerred/monorepo) into .agents/skills/gh-helper in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shepherdjerred/monorepo --skill gh-helper -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gh-helper, .gemini/skills/gh-helper, .github/skills/gh-helper and .opencode/skills/gh-helper in your project.
Going by SKILL.md and its folder, Gh Helper needs the command-line tools its instructions call (gh, git and jq).
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Gh Helper is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.4k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Gh Helper: Extract Repo (archibate/dotfiles-opencode, 108 stars), Subtree Publish (cat-xierluo/legal-skills, 713 stars), Git Project Status (espennilsen/pi, 122 stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
shepherdjerred (a GitHub user) maintains it in shepherdjerred/monorepo, which has 112 GitHub stars. The repository holds 63 skills in this directory. The repository was last updated on October 8, 2026.
Source: shepherdjerred/monorepo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.