skills.rest
cbusillo
cbusilloCOMMUNITY
Explore all skills by this author →
GitHub

github

Executes GitHub repository workflows including PRs, issues, Actions, merges, and cleanup through automation-token helpers.

5|1|Updated May 5, 2026
Search Tags:#automation#code review#github#github actions#pull requests#issues#ci diagnosis
One-click install
npx skills add https://github.com/cbusillo/codex-skills --skill github-cbusillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/cbusillo/codex-skills/tree/main/skills/github
Command: npx skills add https://github.com/cbusillo/codex-skills --skill github-cbusillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Raw gh CLI commands use the active local GitHub account, mangle multiline Markdown bodies, and lack retry, quota, and reconciliation handling. This Skill routes every GitHub operation through body-safe, automation-identity helpers so PRs, issues, comments, merges, and Actions runs are owned by the configured bot account with deterministic JSON envelopes and fail-closed error handling. ## Core Features & Use Cases - PR Lifecycle Management: Create, view, edit, comment, check, merge, and supersede pull requests through the REST-first gh-pr.py helper with safe body-file handling and merge-outcome reconciliation. - Issue and Comment Operations: Create, edit, close, and reopen issues with stdin-backed multiline Markdown, ownership-aware cross-author protections, and duplicate-close support. - CI Diagnosis and Workflow Control: Diagnose failing PR checks, dispatch or watch exact GitHub Actions runs with bounded timeouts, and capture repository snapshots for orientation. - Automation Identity Enforcement: Commit and push as the configured bot identity, route all API calls through a token wrapper that fails closed without automation auth, and enforce command policies that block raw gh mutations. - Use Case: After finishing a feature branch, ask the agent to create a PR with a multiline body, watch its checks, diagnose any CI failure, merge with branch cleanup, and reconcile the local runtime checkout — all under the automation account. ## Quick Start Ask the agent to create a pull request for the current branch with a Markdown body file using the GitHub helper, then check its CI status.

Frequently Asked Questions about github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub PR with a multiline Markdown body from the CLI?▼

Use the gh-pr.py helper with --title and --body-file flags so the body is read from a file rather than quoted in argv. This preserves Markdown formatting and routes the write through the configured automation token instead of the active local account.

How do I diagnose failing GitHub Actions checks on a pull request?▼

Run the github-ci-diagnose.py helper with --pr to read check runs through shared REST readers and summarize relevant job log excerpts. It reports quota or degraded components explicitly in its diagnostic output.

Why should I avoid raw gh pr merge and gh issue create commands?▼

Raw gh commands use the active local GitHub account, can mangle multiline bodies, and skip merge defaults and branch cleanup. The skill's command policies block them and route to helpers that enforce automation identity and safe body handling.

Can I read GitHub secret-scanning alerts without exposing secret values?▼

Yes, the github_read.py secret-scanning-status command requests only open alerts with hide_secret=true and returns a status of clean, findings, unavailable, or not_enabled. It never returns raw alert payloads or detected secret values and requires automation auth.

What happens when a GitHub API write fails with an unknown outcome?▼

Non-idempotent writes use a stable request fingerprint and pre-write snapshot for reconciliation before any retry. Ambiguous results fail closed rather than risking duplicate creates, and the JSON envelope reports write_outcome and recovery state.

When should I use github-plan instead of the github skill?▼

Use github-plan for durable planning work such as roadmaps, blockers, milestones, Projects, and workstream graphs. The github skill covers repository execution: PRs, branches, Actions, reviews, merges, and safe cleanup.

Related Skills

Explore More Software Engineering Skills→
witwave-aiwitwave-ai
2

git-sync-source

Clone or fast-forward a primary Git repository checkout to match its default branch.

Official
Intermediate
doesitscriptdoesitscript

github-issue-workflow

Draft and coordinate cross-repo GitHub issues with labels and cross-links.

Community
Intermediate
mitchellfyimitchellfyi
3

dxwatchpr

Monitor GitHub pull requests for CI failures and unresolved review feedback.

Community
Advanced
pepegarpepegar

apple-mail

Search and read Apple Mail emails and extract attachments from local macOS storage.

Community
Intermediate