skills.rest
arslan9024
arslan9024COMMUNITY
Explore all skills by this author →
GitHub

git-manager

Standardizes Git branching, conventional commits, and autonomous issue resolution workflows.

Updated Jan 8, 2026
Search Tags:#git#ci/cd#version control#conventional commits#github#branching#issue automation
One-click install
npx skills add https://github.com/arslan9024/White-Caves --skill git-manager-arslan9024
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-manager
Source: https://github.com/arslan9024/White-Caves/tree/main/.agents/skills/git-manager
Command: npx skills add https://github.com/arslan9024/White-Caves --skill git-manager-arslan9024

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often struggle with inconsistent commit messages, disorganized branching, and backlogs of unresolved GitHub issues. This Skill enforces a disciplined Git workflow and can autonomously drain open issues using a worker swarm. ## Core Features & Use Cases - Branching Standards: Enforces naming conventions like feature/wave-XX-[name] and fix/[ticket-id]-[name], always branching from the latest main. - Conventional Commits: Generates commit messages following the Conventional Commits standard (feat:, fix:, docs:, chore:, refactor:) scoped to Waves or components. - Autonomous Issue Drainer: Runs scripts/orchestrator/issue-drainer.py with the GitHub CLI to spawn worker agents that branch, code, test, and commit fixes for each open issue. - Use Case: Ask the agent to "drain the backlog" and it queries the GitHub API, dispatches workers per issue, and reports when the swarm completes. ## Quick Start Ask the agent to review the current changes with git status and commit them using a conventional commit message on a new feature branch.

Frequently Asked Questions about git-manager

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

FAQPage Schema
How do I write conventional commit messages for my project?▼

Use prefixes like feat:, fix:, docs:, chore:, or refactor: followed by a scoped description, such as "feat: [Wave] added new feature". Keep each commit focused on a single logical change and reference the relevant Wave or Epic.

How do I automatically resolve open GitHub issues with AI agents?▼

Install and authenticate the GitHub CLI, then run the issue-drainer orchestrator script. It queries the GitHub API and spawns worker agents that autonomously branch, code, test, and commit fixes for each open issue.

What branching strategy should I use for feature development?▼

Create feature branches named feature/wave-XX-[name] and bugfix branches named fix/[ticket-id]-[name]. Always branch from the latest main branch to avoid merge conflicts and stale code.

Does the issue drainer require the GitHub CLI?▼

Yes, the GitHub CLI (gh) must be installed and authenticated before running the issue-drainer script. The script relies on it to query the GitHub API for open issues.

Why should unrelated changes not be combined into one commit?▼

Mixing unrelated changes makes history hard to review, revert, and audit. The workflow requires staging only files related to a specific change and verifying scope with git status and git diff before committing.

Related Skills

Explore More Software Engineering Skills→
hw-native-syshw-native-sys
30

ptoas-publish-pr

Publish scoped PTOAS changes as a draft GitHub pull request.

Official
Advanced
jeisenbackjeisenback

ship

Merge base branch, run tests, bump versions, update CHANGELOG, commit, and create a PR.

Community
Advanced
ils15ils15
10

quality-gate

Run linters, type-checkers, tests, and build steps before code commits.

Community
Advanced
hung-phanhung-phan

trunk-based-development

Implement a trunk-based development workflow with short-lived branches and feature flags.

Community
Advanced