github

KJone1's avatarfrom KJone1

Strict guidelines for all GitHub operations using the `gh` CLI. Covers pull requests, secrets management, and commit conventions. Applied when working with GitHub repositories, creating PRs, managing secrets, or following commit conventions.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 2, 2026

When & Why to Use This Skill

This Claude skill streamlines GitHub workflows by enforcing the use of the `gh` CLI for pull requests, secrets management, and commit conventions. It ensures high-quality contributions through mandatory patterns like PR size limits, structured descriptions, and JIRA-linked titles, optimizing the development lifecycle and team collaboration.

Use Cases

  • Automated PR Creation: Generate standardized pull requests with mandatory summaries, test plans, and size constraints to improve code review efficiency.
  • Workflow Standardization: Enforce consistent commit message formats and branch naming conventions, such as linking JIRA tickets for better project tracking.
  • Secure Secret Management: Handle GitHub secrets and authentication status directly through the CLI, ensuring secure and authorized repository operations.
  • PR Lifecycle Management: Seamlessly transition between draft status and ready-for-review using CLI commands to maintain a clean and organized development pipeline.
namegithub
descriptionUse when asked about GitHub operations, PRs, or commit conventions.
user-invocablefalse

GitHub Operations

MANDATORY: Always use gh CLI for all GitHub operations. Verify gh auth status before starting.

Critical Patterns

  • Use --draft for WIP, gh pr ready when done
  • Keep PRs <400 lines
  • Include Summary + Test plan in PR body
  • PR titles: Match branch format with JIRA ticket if present (e.g., TICKET-123: Add user authentication)
  • Provide context in descriptions