github-operator

Automate Git operations with branch naming and conventional commits.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/aimskr/aims-claude-toolkit --skill github-operator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-operator
Source: https://github.com/aimskr/aims-claude-toolkit/tree/main/skills/github-operator
Command: npx skills add https://github.com/aimskr/aims-claude-toolkit --skill github-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git and GitHub workflow fatigue and human error in repetitive tasks. This Skill automates routine Git operations (status checks, selective staging, commits with conventional messages, pushing, and PR creation) to keep contributor workflows consistent and auditable.

Core Features & Use Cases

  • Enforces branch naming convention feature/JH2-*
  • Performs status/diff checks and commits with selective staging
  • Pushes to origin and creates PRs against dev with a fixed base, ensuring consistency

Quick Start

Use the github-operator to create a feature/JH2-<name> branch, commit changes with conventional messages, push to origin, and open a PR against dev.

Frequently Asked Questions about github-operator

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

FAQPage Schema
What is the best way to manage repetitive Git workflow tasks for team collaboration?

The best way to manage repetitive Git workflow tasks is automating routine operations like status checks, selective staging, and conventional commits. This eliminates workflow fatigue and ensures auditable team collaboration.

How do I automate GitHub pull request creation against a fixed base branch?

Automating GitHub pull request creation involves pushing committed changes to the origin remote and opening a PR against a fixed dev base branch. This reduces manual overhead and ensures consistent contributor workflows.

How do I enforce conventional commit messages and a branch naming convention in Git?

To enforce conventional commit messages and branch naming, you can automate routine Git operations to apply strict formatting rules like feature/JH2-* prefixes. This prevents human error and keeps code collaboration auditable.

Can I use selective staging for Git commits before pushing to a remote repository?

Yes, you can use selective staging for Git commits before pushing. The automation performs status and diff checks, stages specific changes, and commits them with conventional messages to maintain consistency.

Does automated Git workflow require manual interaction for pull request decisions?

Yes, automated Git workflow expects the user to interact specifically for pull request creation decisions. While it automates branching, commits, and pushes, it pauses to let you confirm PR details against the dev branch.

What is the best way to manage repetitive Git workflow tasks for team collaboration?

The best way to manage repetitive Git workflow tasks is automating routine operations like status checks, selective staging, and conventional commits. This eliminates workflow fatigue and ensures auditable team collaboration.