gh-cli

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# GitHub via the `gh` CLI

Use the `gh` CLI for all GitHub operations. `gh api` covers anything without a
dedicated subcommand.

Read freely. An explicit user request that names the GitHub target and a bounded
write action authorizes that action. Otherwise, show the exact mutation and ask
for confirmation before running it.

Always confirm immediately before destructive, irreversible,
privilege-changing, or materially broader work. This includes merges, closing
or deleting content, publishing or deleting releases, changing access or
secrets, and any action whose effects exceed the request. Recheck the repository
and object identifier before every mutation.

## Repos & info

```sh
gh repo view OWNER/REPO
gh api repos/OWNER/REPO
gh search repos "QUERY" --limit 10
gh search code "QUERY"            # cross-repo code search
```

## Issues

```sh
gh issue list --repo OWNER/REPO --state open
gh issue view NUMBER --repo OWNER/REPO --comments
gh issue create --repo OWNER/REPO --title T --body B   # WRITE
gh issue comment NUMBER --body B                        # WRITE
```

## Pull requests

```sh
gh pr list --repo OWNER/REPO
gh pr view NUMBER --comments
gh pr diff NUMBER
gh pr checks NUMBER                 # CI status
gh pr create --base main --head BRANCH --title T --body B   # WRITE
gh pr review NUMBER --approve|--request-changes -b B        # WRITE
gh pr merge NUMBER --squash                                 # HIGH-RISK: confirm
```

## Actions / workflows

```sh
gh run list --repo OWNER/REPO --limit 10
gh run view RUN_ID --log
gh run view RUN_ID --log-failed     # only failed step logs
gh run rerun RUN_ID                 # HIGH-RISK: confirm
gh workflow list
gh workflow run WORKFLOW --ref BRANCH   # HIGH-RISK: confirm
```

## Releases

```sh
gh release list --repo OWNER/REPO
gh release view TAG
gh release create TAG --notes N     # HIGH-RISK: confirm
```

## Code scanning / security (via gh api)

```sh
gh api repos/OWNER/REPO/code-scanning/alerts --paginate
gh api repos/OWNER/REPO/code-scanning/alerts/ALERT_NUMBER
gh api repos/OWNER/REPO/dependabot/alerts --paginate
```

## Tips

- `--json FIELDS --jq '...'` for structured output:
  `gh pr list --json number,title,headRefName --jq '.[] | .title'`.
- `gh api --paginate` to traverse all pages.
- Authentication uses the existing `gh auth` session / `$GITHUB_TOKEN`.

From nb-99/skillektion, MIT.

More from nb-99/skillektion