Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

gh-cli

Étoiles3

Forks0

Mis à jour12 juin 2026 à 14:57

Use when working with GitHub from the command line with gh for auth, repo/issue/PR triage, reviews, inline review comments, Actions, releases, API requests, aliases, and automation.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

gabrielfruet

gabrielfruet/.dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	gh-cli
description	Use when working with GitHub from the command line with gh for auth, repo/issue/PR triage, reviews, inline review comments, Actions, releases, API requests, aliases, and automation.

gh-cli

Use gh for GitHub tasks. Prefer JSON + jq for scripted output.

Rules

Check auth first: gh auth status.
Use gh <group> --help when unsure.
Prefer --json, --jq, --template, and --paginate.
Use gh pr ... for PR work.
In a PR context, "comments" usually means inline review comments (line-level notes on the diff), NOT the top-level PR conversation. Fetch them with gh api repos/<owner>/<repo>/pulls/<num>/comments --paginate. gh pr view --comments and gh issue view --comments return only the conversation, not the review.
If gh repeatedly times out against api.github.com due a bad DNS-resolved IP, verify with curl -I https://api.github.com; as a last resort, use the GitHub REST API with curl --resolve api.github.com:443:<reachable-ip> and an auth token from gh auth token.
For new PRs, push the branch first; gh pr create needs a remote branch. Use --head only for an already-pushed branch.
For multiline PR bodies, prefer --body-file (or a heredoc/file) instead of inline --body to avoid literal \n in GitHub.
For existing PRs, use gh pr view <branch-or-number> --json isDraft,number,title,url,body and gh pr edit <number> --body-file <file>.
Scope cross-repo work with --repo owner/name.

Triage recipes

gh repo view --json nameWithOwner,url -q '.nameWithOwner + " " + .url'
gh issue list --state all --limit 20 --json number,title,state,labels,author
gh pr list --state open --limit 20 --json number,title,author,updatedAt
gh pr list --state merged --limit 20 --json number,title,mergedAt,author

Review inspection

gh pr view 123 --json reviews,comments,files                 # top-level conversation + review summaries
gh api repos/<owner>/<repo>/pulls/123/comments --paginate    # INLINE review comments (line-level, the "review")

"Review comments" = line-level notes on the PR diff. Fetched via the PR comments API above. They are NOT returned by gh pr view --comments.
"Issue / conversation comments" = the top-level PR discussion. Fetched via gh pr view --comments or gh issue view --comments.
When a user asks to "look at the comments" / "check the comments" / "see the review" on a PR, default to review comments, not the conversation.
Group by reviewer; ignore empty/bot noise when summarizing.
If review data looks incomplete, fall back to gh api repos/<owner>/<repo>/pulls/<num>/reviews.

Common commands

gh auth login
gh auth status
gh repo clone owner/repo
gh pr view 123 --web
gh pr view <branch> --json isDraft,number,title,url,body
gh pr checkout 123
gh run list
gh run view <run-id> --log
gh release list
gh api /user --jq '.login'
gh alias set prview 'pr view --web'
gh completion -s zsh

Plus depuis ce dépôt

même dépôt

pr-workflow

gabrielfruet/.dotfiles

Use when opening a PR and driving it to green CI — push the branch, write a high-level PR description, watch checks, fix failures, and keep looping until green; also use when an already-open PR gets new commits.

2026-07-163

task-memory

gabrielfruet/.dotfiles

Use when the user starts, resumes, switches, saves, or recalls a named task or ongoing work across sessions (e.g. "remember this", "continue X", "what was I doing on Y", "track this task").

2026-07-133

git-workflow

gabrielfruet/.dotfiles

Git commit workflow. Load when finishing any code-change task (after verification) to commit and push, or when explicitly staging/committing.

2026-07-133

lightly-repos-workflow

gabrielfruet/.dotfiles

Use when modifying or adding a transform, loss, model, method, package, task-model, config, docs page, or example in a Lightly AG repo (lightly-ssl or lightly-train) and you need repo-specific conventions.

2026-07-103

subagent

gabrielfruet/.dotfiles

Spawn a subagent to run a task. Use when you want to delegate work to a separate pi instance.

2026-07-103

ltdetr-coco-recipe

gabrielfruet/.dotfiles

Use when configuring or replicating LT-DETR v2 (ltdetrv2-s/m/l/x) COCO benchmarks via the lightly-train wrapper — model alias map, global vs per-rank batch size, recipe invariants, ECDet config mapping, cluster pins, and common gotchas.

2026-07-103

gh-cli

Use gh for GitHub tasks. Prefer JSON + jq for scripted output.

Rules

Check auth first: gh auth status.

Use gh <group> --help when unsure.

Prefer --json, --jq, --template, and --paginate.

Use gh pr ... for PR work.

In a PR context, "comments" usually means inline review comments (line-level notes on the diff), NOT the top-level PR conversation. Fetch them with gh api repos/<owner>/<repo>/pulls/<num>/comments --paginate. gh pr view --comments and gh issue view --comments return only the conversation, not the review.

If gh repeatedly times out against api.github.com due a bad DNS-resolved IP, verify with curl -I https://api.github.com; as a last resort, use the GitHub REST API with curl --resolve api.github.com:443:<reachable-ip> and an auth token from gh auth token.

For new PRs, push the branch first; gh pr create needs a remote branch. Use --head only for an already-pushed branch.

For multiline PR bodies, prefer --body-file (or a heredoc/file) instead of inline --body to avoid literal \n in GitHub.

For existing PRs, use gh pr view <branch-or-number> --json isDraft,number,title,url,body and gh pr edit <number> --body-file <file>.

Scope cross-repo work with --repo owner/name.

Triage recipes

gh repo view --json nameWithOwner,url -q '.nameWithOwner + " " + .url' gh issue list --state all --limit 20 --json number,title,state,labels,author gh pr list --state open --limit 20 --json number,title,author,updatedAt gh pr list --state merged --limit 20 --json number,title,mergedAt,author

Review inspection

gh pr view 123 --json reviews,comments,files # top-level conversation + review summaries gh api repos/<owner>/<repo>/pulls/123/comments --paginate # INLINE review comments (line-level, the "review")

"Review comments" = line-level notes on the PR diff. Fetched via the PR comments API above. They are NOT returned by gh pr view --comments.

"Issue / conversation comments" = the top-level PR discussion. Fetched via gh pr view --comments or gh issue view --comments.

When a user asks to "look at the comments" / "check the comments" / "see the review" on a PR, default to review comments, not the conversation.

Group by reviewer; ignore empty/bot noise when summarizing.

If review data looks incomplete, fall back to gh api repos/<owner>/<repo>/pulls/<num>/reviews.

Common commands

gh auth login gh auth status gh repo clone owner/repo gh pr view 123 --web gh pr view <branch> --json isDraft,number,title,url,body gh pr checkout 123 gh run list gh run view <run-id> --log gh release list gh api /user --jq '.login' gh alias set prview 'pr view --web' gh completion -s zsh