Run any Skill in Manus with one click

Get Started

github

Stars11

Forks4

UpdatedApril 29, 2026 at 13:24

Interact with GitHub using the `gh` CLI. Use for issues, PRs, CI runs, releases, and advanced API queries.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

aretw0

aretw0/agents-lab

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	github
description	Interact with GitHub using the `gh` CLI. Use for issues, PRs, CI runs, releases, and advanced API queries.

GitHub Skill

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not inside a git directory, or pass URLs directly.

Disable interactive prompts in agent-run commands:

GH_PROMPT_DISABLED=1 gh <command>

Board-first issue mirroring

When this workspace uses .project/tasks.json as the canonical board, treat GitHub Issues as an external mirror unless the operator explicitly says otherwise.

Mapping:

GitHub issue number/URL -> task note/evidence external reference.
GitHub issue title -> task description summary, preserving local task id as canonical id.
GitHub labels -> task priority/milestone only through an explicit mapping recorded in the task notes.
GitHub state closed/open -> mirror of local status, not an auto-close authority.

Sync policy:

Prefer .project -> GitHub for publication/mirror updates.
Never close local tasks solely because a GitHub issue is closed; require local verification evidence.
On conflict, append an audit note and ask for/rely on the board policy rather than overwriting silently.
Do not mutate public GitHub metadata or issue state without explicit operator intent.

Issues

# List open issues
gh issue list --repo owner/repo

# View an issue
gh issue view 42 --repo owner/repo

# Create an issue
GH_PROMPT_DISABLED=1 gh issue create --title "..." --body "..." --repo owner/repo

# Close an issue
gh issue close 42 --repo owner/repo

Pull Requests

# List PRs
gh pr list --repo owner/repo

# View a PR
gh pr view 55 --repo owner/repo

# Create a PR (always provide title and body — never rely on interactive editor)
GH_PROMPT_DISABLED=1 gh pr create --title "..." --body "..." --repo owner/repo

# Check CI status on a PR
gh pr checks 55 --repo owner/repo

# Merge a PR
GH_PROMPT_DISABLED=1 gh pr merge 55 --squash --delete-branch --repo owner/repo

CI / Workflow Runs

# List recent runs
gh run list --repo owner/repo --limit 10

# View a specific run
gh run view <run-id> --repo owner/repo

# View only failed step logs
gh run view <run-id> --repo owner/repo --log-failed

JSON Output

Most commands support --json with --jq for structured filtering:

gh issue list --repo owner/repo --json number,title,state \
  --jq '.[] | "\(.number): \(.title) [\(.state)]"'

gh pr list --repo owner/repo --json number,title,headRefName \
  --jq '.[] | "\(.number) [\(.headRefName)]: \(.title)"'

API for Advanced Queries

Use gh api for anything not covered by subcommands:

# Get PR details
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

# List labels
gh api repos/owner/repo/labels --jq '.[].name'

# Paginated results
gh api --paginate repos/owner/repo/issues --jq '.[].title'

More from this repository

same repository

pi-workflows-sovereign

aretw0/agents-lab

First-party, sovereign workflows form — author, list, and validate multi-step workflow specs (YAML, DAG of block/command/agent steps with typed I/O). Use when writing or checking .workflows/*.workflow.yaml. Execution (running workflows) is delivered by SP2; this slice provides the form (workflow_list, workflow_validate).

2026-06-2311

colony-dogfood

aretw0/agents-lab

Conduz um experimento de dogfood onde a colônia Pi executa uma task do .project/tasks.json em dois tempos (research → código) com gates do operador. Use quando o operador quiser ativar um experimento colony-experiment-phase1 ou colony-experiment-phase2.

2026-06-1811

control-plane-continuity

aretw0/agents-lab

Use when a Pi session needs to continue local-safe work with low operator friction: discover focus, interview only for missing constraints, prepare bounded slices, use workers only behind gates, checkpoint, and stop on real risk.

2026-05-2711

web-browser

aretw0/agents-lab

Interact with web pages via browser automation: navigate, click, fill forms, screenshot, and evaluate JavaScript. Uses Chrome/Chromium remote debugging (CDP).

2026-05-2311

control-plane-ops

aretw0/agents-lab

Operar o control-plane local-first do agents-lab com board canônico, long-runs bounded, handoff/checkpoint, rollout/rollback e espelhos externos sem perder governança.

2026-05-2211

cultivate-primitive

aretw0/agents-lab

Guia o cultivo de uma primitiva reutilizável. Use quando o usuário identificar um padrão recorrente que merece ser extraído como skill, extensão ou convenção.

2026-05-2211

name	github
description	Interact with GitHub using the `gh` CLI. Use for issues, PRs, CI runs, releases, and advanced API queries.

GitHub Skill

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not inside a git directory, or pass URLs directly.

Disable interactive prompts in agent-run commands:

GH_PROMPT_DISABLED=1 gh <command>

Board-first issue mirroring

When this workspace uses .project/tasks.json as the canonical board, treat GitHub Issues as an external mirror unless the operator explicitly says otherwise.

Mapping:

GitHub issue number/URL -> task note/evidence external reference.
GitHub issue title -> task description summary, preserving local task id as canonical id.
GitHub labels -> task priority/milestone only through an explicit mapping recorded in the task notes.
GitHub state closed/open -> mirror of local status, not an auto-close authority.

Sync policy:

Prefer .project -> GitHub for publication/mirror updates.
Never close local tasks solely because a GitHub issue is closed; require local verification evidence.
On conflict, append an audit note and ask for/rely on the board policy rather than overwriting silently.
Do not mutate public GitHub metadata or issue state without explicit operator intent.

Issues

# List open issues
gh issue list --repo owner/repo

# View an issue
gh issue view 42 --repo owner/repo

# Create an issue
GH_PROMPT_DISABLED=1 gh issue create --title "..." --body "..." --repo owner/repo

# Close an issue
gh issue close 42 --repo owner/repo

Pull Requests

# List PRs
gh pr list --repo owner/repo

# View a PR
gh pr view 55 --repo owner/repo

# Create a PR (always provide title and body — never rely on interactive editor)
GH_PROMPT_DISABLED=1 gh pr create --title "..." --body "..." --repo owner/repo

# Check CI status on a PR
gh pr checks 55 --repo owner/repo

# Merge a PR
GH_PROMPT_DISABLED=1 gh pr merge 55 --squash --delete-branch --repo owner/repo

CI / Workflow Runs

# List recent runs
gh run list --repo owner/repo --limit 10

# View a specific run
gh run view <run-id> --repo owner/repo

# View only failed step logs
gh run view <run-id> --repo owner/repo --log-failed

JSON Output

Most commands support --json with --jq for structured filtering:

gh issue list --repo owner/repo --json number,title,state \
  --jq '.[] | "\(.number): \(.title) [\(.state)]"'

gh pr list --repo owner/repo --json number,title,headRefName \
  --jq '.[] | "\(.number) [\(.headRefName)]: \(.title)"'

API for Advanced Queries

Use gh api for anything not covered by subcommands:

# Get PR details
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

# List labels
gh api repos/owner/repo/labels --jq '.[].name'

# Paginated results
gh api --paginate repos/owner/repo/issues --jq '.[].title'