Manage GitHub issues and pull requests, proposed code changes, using the gh command-line tool. Create and inspect discussions, check automated test results, investigate failed logs, rerun jobs, and track authorized merges through to their verified status.
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
Use github to list and inspect GitHub issues and pull requests (PRs), which are requests to incorporate code changes. It can create issues and PRs, post comments, and retrieve PR differences, reviews, and check results. For CI runs, such as automated tests, it examines results and failure logs and reruns failed jobs. It also covers calling the API with gh api to track authorized merges and verify their final state.
Use it to document bugs or proposed changes on GitHub, check review progress, or investigate failed tests. During a merge, it distinguishes between waiting, entering a queue, and completing the merge.
Install gh and authenticate with GitHub. Use git for local commits and branch operations, and code-reading tools for detailed code reviews. Merges must follow repository procedures, required reviews and checks, and the authorized scope. Set GH_CONFIG_DIR if the execution service and user use different authentication configuration locations.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Use gh for GitHub. Use git for local commits/branches/push/pull. Use code-reading tools for deep reviews.
gh auth status
gh auth login
Gateway HOME can differ from operator HOME. If gh auth exists elsewhere, set GH_CONFIG_DIR in the gateway service env and restart.
gh pr list --repo owner/repo --json number,title,state,author,url
gh pr view 55 --repo owner/repo --json title,body,author,files,commits,reviews,reviewDecision
gh pr checks 55 --repo owner/repo
gh pr diff 55 --repo owner/repo
gh pr create --repo owner/repo --title "feat: title" --body-file /tmp/pr.md
When creating or refreshing a PR body, append this final footer only when the Runtime line supplies sessionUrl=<exact-url>. Replace <sessionUrl> with that URL verbatim; do not construct or modify it. sessionUrl is supplied only for an explicitly public session. Omit the footer when it is absent; never substitute a private chat URL or enable sharing to obtain one. Preserve any publication marker before exactly one footer, and keep the footer final:
---
[View the OpenClaw team session](<sessionUrl>)
URLs work directly: gh pr view https://github.com/owner/repo/pull/55.
Use the repository's native landing workflow when provided. For authorized
programmatic merges elsewhere, use GitHub's async merge API
through gh api; gh pr merge does not select this API. Supply the reviewed head
SHA, preserve required reviews/checks, and check stack membership first: submitting
a stacked PR also merges or queues its open downstack PRs, which need their own
review and authorization.
gh api -H 'X-Octopool-Require: merge-async-v1' \
--method PUT repos/owner/repo/pulls/55/merge-async \
-H 'X-GitHub-Api-Version: 2026-03-10' \
-f sha=REVIEWED_HEAD_SHA -f merge_method=squash -f merge_action=direct_merge
gh api -H 'X-Octopool-Require: merge-async-v1' \
repos/owner/repo/pulls/55/merge-async/REQUEST_UUID \
-H 'X-GitHub-Api-Version: 2026-03-10' -H 'Cache-Control: max-age=0'
Keep the Octopool guard header first after api. Protected older wrappers reject
it before they can rewrite merge authority; use an Octopool build containing
the async guard if it is refused.
The supported wrapper preserves SHA/method/action/bypass and only rewrites commit
text. Native gh can pass the header through. Do not remove it, disable policy,
or select a raw binary to work around a rejection.
Retain details.uuid from a 202 response before polling. pending means wait;
merged includes details.sha, which still needs final PR/head verification.
enqueued means queued, not merged: monitor the PR itself. To honor a configured
queue, use merge_action=default (or merge_queue to explicitly enqueue), omitting
direct-only method/title/message fields. Never enable bypass_rules without authorization.
On failed, report details.message. A 409 identifies an existing request;
inspect its UUID and options without resubmitting. Lost replies, polling errors,
and result expiry after 24 hours require reconciliation, never a blind retry or
synchronous fallback. Poll with bounded waits and fresh reads. Async processing
does not arm auto-merge for unmet checks; use the native workflow or gh pr merge --auto when that behavior is authorized.
When the user asks to land or merge a PR, the terminal outcome is the PR's verified GitHub state, not the end of a review, worker turn, or CI observation.
gh pr view ... --json state,mergedAt,mergeCommit
proves state is MERGED.gh issue list --repo owner/repo --state open --json number,title,labels,url
gh issue view 42 --repo owner/repo --json title,body,comments,labels,state
gh issue create --repo owner/repo --title "Bug: ..." --body-file /tmp/issue.md
gh issue comment 42 --repo owner/repo --body-file /tmp/comment.md
gh issue close 42 --repo owner/repo --comment "Fixed in ..."
gh run list --repo owner/repo --limit 10
gh run view <run-id> --repo owner/repo --json status,conclusion,headSha,url
gh run view <run-id> --repo owner/repo --log-failed
gh run rerun <run-id> --repo owner/repo --failed
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'
gh api repos/owner/repo/labels --jq '.[].name'
gh api --cache 1h repos/owner/repo --jq '{stars: .stargazers_count, forks: .forks_count}'
Use --json + --jq for structured output. Use --body-file for comments/bodies containing backticks, shell snippets, env names, or user text.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set up and authenticate the 1Password CLI, then supply stored passwords and API keys to commands or configuration. The skill covers desktop integration, service accounts, and interactive sign-in while keeping secrets out of chat and logs.
Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.
Add a model provider to OpenClaw and verify it with a real response. The skill validates configuration, keeps credentials in environment or file references, and reports test results and any default model changes.
Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.
Manage Apple Notes on macOS through memo, a command-line tool. Create, browse, search, edit, delete, and move notes between folders, or export selected notes to HTML or Markdown for use outside the app.
Manage Apple Reminders from your Mac with remindctl, a terminal tool. View tasks by date, add or edit reminders, organize lists, and mark tasks complete or delete them, including personal to-dos that sync to iOS.