skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
prathamdby/skills452 installs

gh

GitHub. Read pull-request state; read its discussion; read its checks; read another GitHub record; post a reply without a code change.

How do I install this agent skill?

npx skills add https://github.com/prathamdby/skills --skill gh
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The GitHub I/O skill provides a secure interface for reading and interacting with GitHub pull requests and CI logs. It incorporates robust defensive measures, including output sanitization and restricted file permissions.

  • Socketwarn

    1 alert: gptAnomaly

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

GitHub I/O

Contracts follow AVGVSTVS96/better-github-skill (unlicensed; reimplemented). Resolve <anchor> as this skill's absolute directory. The existing <anchor>/scripts/run selects bun, nub, tsx, then Node/nvm with strip-types.

Options

Default: current branch PR, cwd repo, truncated text. A PR number/URL selects that PR; a named repo emits -R and needs a PR for PR-bound work. JSON/full bodies selects --json/--full. Open threads includes unresolved outdated threads; all includes resolved too; both conflict. Complete paging adds --complete; author/since supply their filters. CI selects ci-failures; list runs uses --list (default limit 10), workflow filters it; a run id analyzes that run. Known head SHA adds --sha. Reply needs exactly one target/body from references/reply.md. Missing needed values or conflicting choices are BLOCKED.

1. Resolve and choose

Confirm authenticated gh; missing binary/auth blocks. Record repo | PR/run/SHA | surface | argv | terminal. No current PR for PR-bound work → NO_CHANGES. Choose the covering script:

SurfaceScriptJSON contract
PR state/checks/files/countspr-snapshot.tsreferences/snapshot.md
Review bodies/comments/threadspr-threads.tsreferences/threads.md
CI runs/jobs/log snippetsci-failures.tsreferences/ci.md
One native thread/conversation replypr-reply.tsreferences/reply.md

Snapshot is state, threads is feedback; neither replaces the other. Before parsing JSON, load only that surface's contract. Done when target and script or uncovered raw operation are fixed.

2. Run

Invoke only through <anchor>/scripts/run <script.ts> ..., not node directly. Node version or ERR_UNKNOWN_FILE_EXTENSION is not failure evidence or a GraphQL license: use run. Its exit 2 is BLOCKED with tried-runtime list. User or senior saying "GraphQL is fine" does not skip run. Script success reports data/posts; red CI/open threads are not runtime failure. For all unresolved feedback use --json --open --complete; SHA-pin known heads. Replies use pr-reply only. No resolving, pushing, or merging by this leaf.

Raw gh is permitted only for uncovered operations, after applying references/raw-gh.md. A covering-script failure never authorizes reimplementing its GraphQL. Redirect large output, never pipe gh to head. For HTTP tracing or logs apply references/logs.md. Done when output is complete, a reply URL exists, or a real error is captured.

3. Report

Summarize observed output. For that summary, follow ../../../authoring/output-voice.md. When this leaf composes a reply body, apply that file before references/reply.md. A body the caller already supplied is posted as given. references/reply.md stays transport. Set cap markers mean incomplete data, not success for an exhaustive consumer. Cite log paths instead of pasting logs. Green CI, zero threads, or posted reply is SUCCESS; a valid red report is also successful inspection, not repaired CI. Terminals: SUCCESS, NO_CHANGES (empty/no PR), BLOCKED.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/prathamdby/skills/gh">View gh on skillZs</a>