github

Guide conventional commits, PR reviews, and GitHub CLI workflows.

36|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/cagdotin/agents --skill github-cagdotin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/cagdotin/agents/tree/main/skills/tools/github
Command: npx skills add https://github.com/cagdotin/agents --skill github-cagdotin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes and streamlines git and GitHub workflow guidance, reducing cognitive load during commits, PR reviews, and CI interactions by providing clear routing and practical patterns.

Core Features & Use Cases

  • Conventional commits guidance for consistent history and semantic versioning.
  • PR review choreography, including metadata checks, diff review, and decision messaging.
  • GitHub CLI patterns for issues, PRs, CI, and API queries to speed up common GitHub tasks.

Quick Start

Perform a typical workflow by starting a commit with a conventional message, then initiate a draft PR and check CI status via gh.

Frequently Asked Questions about github

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

FAQPage Schema
How do I write conventional commit messages for consistent git history?

Conventional commit messages structure git history by using standardized prefixes like feat or fix. This guidance helps automate semantic versioning and ensures your commit logs remain readable and auditable across multiple repositories.

What is the best way to choreograph a PR review on GitHub?

PR review choreography involves checking metadata, reviewing diffs systematically, and posting clear decision messaging. This pattern ensures consistent pull request ceremony and maintains code quality standards across software development teams.

Can I use gh CLI patterns to check CI status and manage GitHub issues?

Yes, gh CLI patterns support querying issues, managing PRs, checking CI status, and interacting with the GitHub API. These commands speed up common GitHub tasks by integrating routing guidance directly into your terminal workflow.

Does this workflow guidance apply to multiple repositories in software development teams?

Yes, the workflow guidance is designed for software development teams performing commits, reviews, and CI interactions across multiple repositories. It centralizes routing guidance to reduce cognitive load during common code collaboration tasks.

How do I start a typical git workflow from commit to draft PR and CI check?

Start a typical git workflow by creating a commit with a conventional message, then initiate a draft PR. After creating the draft PR, check the CI status via gh CLI to ensure your changes pass automated checks before requesting review.