القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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").
Git commit workflow. Load when finishing any code-change task (after verification) to commit and push, or when explicitly staging/committing.
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.
Spawn a subagent to run a task. Use when you want to delegate work to a separate pi instance.
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.
| 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. |
Use gh for GitHub tasks. Prefer JSON + jq for scripted output.
gh auth status.gh <group> --help when unsure.--json, --jq, --template, and --paginate.gh pr ... for PR work.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.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.gh pr create needs a remote branch. Use --head
only for an already-pushed branch.--body-file (or a heredoc/file) instead of inline --body to avoid literal \n in GitHub.gh pr view <branch-or-number> --json isDraft,number,title,url,body and gh pr edit <number> --body-file <file>.--repo owner/name.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
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")
gh pr view --comments.gh pr view --comments or gh issue view --comments.gh api repos/<owner>/<repo>/pulls/<num>/reviews.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