Skip to content
cccskills
FreePublished on GitHub

github

Interact with GitHub repos, PRs, issues, CI, and notifications via the pi-github extension commands and gh CLI. Use when asked to check PRs, list issues, view repo status, check CI, browse notifications, create or merge PRs, fix PR review feedback, or perform any GitHub operation. **Triggers:** "open PRs", "repo status", "CI status", "merge PR", "fix PR", "fix PRs", "fix review feedback", "create PR", "GitHub notifications", any /gh-* command, or when a GitHub PR URL is shared.

The English summary is being prepared. Showing the original description.

Works withGitHub
See how to install

Files included (9)

  • SKILL.md4.0 KB
  • references/pr-create.md1.2 KB
  • references/pr-fix-parallel.md7.8 KB
  • references/pr-fix.md4.8 KB
  • references/pr-merge.md2.9 KB
  • scripts/check-conflicts.sh997 B
  • scripts/fetch-threads.sh2.7 KB
  • scripts/reply-thread.sh1.1 KB
  • scripts/resolve-thread.sh1.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

GitHub — pi-github Extension

The pi-github extension provides /gh-* commands for common GitHub operations. All commands also work as /github-* variants.

Prerequisites

  • gh CLI installed and authenticated
  • For repo-scoped commands: run from a git repo, or specify the repo

Commands + Agent Tools

The pi-github extension provides /gh-* commands for user-initiated operations and LLM tools for agentic workflows (PR review thread resolution).

Commands

CommandWhat it does
/gh-prs [mine|review-requested] [repo]List open PRs
/gh-issues [mine|label:name] [repo]List open issues
/gh-status [repo]Repo dashboard: PRs, issues, CI, branch PR
/gh-actions [branch] [repo]Recent workflow runs
/gh-notificationsUnread GitHub notifications
/gh-pr-create [base]Create PR with LLM-generated summary
/gh-pr-review [number|repo#N|URL]Show PR review feedback
/gh-pr-fix [number|repo#N|URL]Fix unresolved review threads
/gh-pr-merge [number|repo#N|URL] [--squash|--merge|--rebase]Merge PR + full cleanup

PR Thread Tools (for agents fixing review feedback)

These tools use gh CLI under the hood — no API tokens needed. Always prefer these over raw REST/GraphQL calls.

ToolPurpose
github_review_thread_replyReply to a PR review thread (thread_id, message)
github_resolve_review_threadMark a review thread as resolved (thread_id) — MANDATORY after each fix
github_post_pr_commentPost a summary comment on a PR (owner, repo, pr_number, body)

Repo Reference Syntax

Commands accept flexible repo/PR references anywhere in args:

FormatExample
GitHub URLhttps://github.com/owner/repo/pull/123
Owner/repo#Nespennilsen/pi#96
Repo#N (with default owner)pi#96
Owner/repoespennilsen/pi
Plain number96
No argsAuto-detect from current branch

Default Owner

Set in settings.json to skip typing the owner:

{ "pi-github": { "defaultOwner": "espennilsen" } }

Detailed Workflows

For complex PR operations, see the reference docs:

  • Fixing PR review threads — references/pr-fix.md Read when fixing unresolved review feedback, resolving threads, or using /gh-pr-fix. ⚠️ Mandatory: after pushing code fixes, resolve ALL threads via GraphQL resolveReviewThread.

  • Parallel PR fixes — references/pr-fix-parallel.md Read when fixing review feedback across multiple PRs simultaneously using parallel subagents (pool or orchestrator mode).

  • Merging PRs — references/pr-merge.md Read when merging a PR, resolving merge conflicts, cleaning up branches/worktrees, or using /gh-pr-merge.

  • Creating PRs — references/pr-create.md Read when creating a PR with a generated summary, or using /gh-pr-create.

Raw gh CLI

For anything the commands don't cover:

# Structured output
gh pr list --json number,title --jq '.[] | "#\(.number) \(.title)"'

# GraphQL
gh api graphql -f query='{ viewer { login } }'

# API calls
gh api repos/owner/repo/contributors --jq '.[].login'

Conventions

  • Default merge strategy: squash
  • Tag releases as v<semver>
  • Use --json + --jq for structured output
  • Always use worktrees for feature branches — never git checkout in main dir

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audit, generate, update, and lint AGENTS.md files across all projects. Use when asked to check project context files, scaffold AGENTS.md for new projects, update stale ones, or run a cross-project audit.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

Draft, edit, and publish blog posts for e9n.dev. Use when creating new posts, editing drafts, or refining existing content. Handles Eleventy frontmatter, Tailwind formatting, and Espen's authentic voice.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

Generate a full operational status report for the Aivena bot. Checks all subsystems: extensions, webserver, Telegram, chat bridge, heartbeat, cron, database, memory, CRM, calendar, task management, jobs/telemetry, and storage. **Triggers — use this skill when:** - User asks for "status", "bot status", "system status", "operational status" - User asks "is everything running?", "how's Aivena doing?" - User says "health check", "diagnostics", "systems check" - User asks "what's the state of the bot?"

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

cmux

Free

Orchestrate cmux terminal panes — split terminals, run parallel processes, read output from other panes, and use the built-in browser. Use when working inside cmux and you need to run a dev server, watch tests, spawn sub-agents, or preview web pages.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

Review code for quality, security, performance, and maintainability. Use when reviewing PRs, auditing a codebase, or refactoring. Covers TypeScript, Node.js, infrastructure-as-code, and full-stack web apps.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

See all skills by espennilsen

Report a problem with this skill