GitHub Integrationv1.0.0

Work with GitHub through the gh CLI - read and triage issues, summarise pull requests, check CI status, and draft issues or PR descriptions. Use when the user mentions GitHub issues, PRs, CI checks, releases, or asks for a repository activity summary.

Author: Velonx
License: MIT
Updated: Sep 25, 2026

github devops issues pull-requests

View on GitHubInstall

Overview

Uses the official gh CLI for common GitHub tasks so the agent works with the user's existing authentication and permissions — no tokens in prompts or files.

When to Use

"What's open on the repo?", "summarise PR #42", "why is CI failing?", "draft an issue for this bug"
Weekly repo activity summaries and triage.

Installation

coming soonVelonx CLI:velonx install github-integration

Get the skill folder
git clone --depth 1 https://github.com/velonx/agent-skills.git
The skill is agent-skills/skills/github-integration/. Or open it on GitHub and download the files.
Give SKILL.md to your agent as instructions
Add it to the system prompt, custom instructions or rules file your agent reads. Keep the rest of the folder next to it if the skill refers to examples or scripts.
Ask for the task in your own words
The agent follows the skill when your request matches it. You can also name it: “use github-integration”.

Get the skill folder
git clone --depth 1 https://github.com/velonx/agent-skills.git
The skill is agent-skills/skills/github-integration/. Or open it on GitHub and download the files.
Claude Code: copy it into a skills folder
cp -R agent-skills/skills/github-integration ~/.claude/skills/
Use .claude/skills/ inside a project instead to share it with your team through git.
Claude apps: upload it
Zip the folder and upload it under Settings → Capabilities → Skills.
Ask for the task in your own words
The agent follows the skill when your request matches it. You can also name it: “use github-integration”.

Get the skill folder
git clone --depth 1 https://github.com/velonx/agent-skills.git
The skill is agent-skills/skills/github-integration/. Or open it on GitHub and download the files.
ChatGPT: add it to a GPT or project
Paste SKILL.md into the instructions, and upload files from the folder as knowledge if the skill uses them.
API: send it as instructions
Use SKILL.md as the system / developer message, or as agent instructions in your SDK.
Ask for the task in your own words
The agent follows the skill when your request matches it. You can also name it: “use github-integration”.

Get the skill folder
git clone --depth 1 https://github.com/velonx/agent-skills.git
The skill is agent-skills/skills/github-integration/. Or open it on GitHub and download the files.
Gemini app: create a Gem
Paste SKILL.md into the Gem’s instructions.
Gemini CLI or API
Add the contents to your project’s GEMINI.md, or pass it as the system_instruction in the API.
Ask for the task in your own words
The agent follows the skill when your request matches it. You can also name it: “use github-integration”.

Get the skill folder
git clone --depth 1 https://github.com/velonx/agent-skills.git
The skill is agent-skills/skills/github-integration/. Or open it on GitHub and download the files.
Add it as a project rule
Create .cursor/rules/github-integration.mdc and paste the body of SKILL.md. Use the skill’s description as the rule description so the agent applies it when relevant.
Keep the folder in your repo
Only needed if the skill refers to examples or scripts.
Ask for the task in your own words
The agent follows the skill when your request matches it. You can also name it: “use github-integration”.

Agents move these settings between versions — if a path doesn’t match, check your agent’s docs.

Usage

Always read before you write. Anything that changes GitHub state (comment, label, close, merge, create) must be shown to the user and confirmed first.

Check access: gh auth status. If not logged in, ask the user to run gh auth login themselves — never handle their token.
Read with JSON output so results are parseable:
- Issues: gh issue list --state open --limit 50 --json number,title,labels,updatedAt
- PRs: gh pr list --json number,title,author,isDraft,reviewDecision
- One PR: gh pr view 42 --json title,body,files,commits,reviews and gh pr diff 42
- CI: gh pr checks 42, then gh run view <run-id> --log-failed
Summarise: group issues by label/theme; for PRs give purpose, size, review state and blockers; for CI quote the failing step and the first real error line.
Draft issues/PR bodies as Markdown: context, steps to reproduce or change summary, expected vs actual, checklist.
Write only after confirmation, e.g. gh issue create --title "…" --body-file draft.md.

Examples

Prompt: "Why is CI red on my PR?" The agent runs gh pr checks, finds the failing job, pulls --log-failed, and reports: "test (node 20) fails in orders.test.ts:41 — expected 403, got 200", with the likely cause.

Requirements & compatibility

Your agent needs

Run shell commands
GitHub CLI (gh), signed in

Environment: Requires the GitHub CLI (gh) installed and authenticated with gh auth login.

Written for

GenericClaudeOpenAIGeminiCursor

gh installed and authenticated by the user.

Limitations

Limited to what the user's gh account can see and do.
Large logs are truncated to the failing step.

Files

SKILL.md

Changelog

1.0.0 — Initial release.

Contributing

This skill lives in velonx/agent-skills. Improvements go through a pull request, reviewed by maintainers.

Edit this skill Report a problem Contributing guide