git-maker

Group, stage, commit, and push Git changes with Conventional Commits.

3|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/alpoxdev/hypercore-skills --skill git-maker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-maker
Source: https://github.com/alpoxdev/hypercore-skills/tree/main/skills/git-maker
Command: npx skills add https://github.com/alpoxdev/hypercore-skills --skill git-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the friction of manual, multi-step Git operations by automating the grouping, staging, committing, and pushing of changes in a single, safe, and verifiable action.

Core Features & Use Cases

  • Intelligent Grouping: Automatically partitions changes into logical Conventional Commits per repository.
  • Worktree Support: Correctly handles linked Git worktrees by identifying checkout roots rather than common git directories.
  • Safety Guardrails: Prevents unsafe operations like force-pushing to protected branches (main/master) and ensures all commits succeed before any push is attempted.
  • Use Case: When you have multiple feature changes across a monorepo or linked worktrees, simply trigger this skill to have the agent group your work, commit with proper Conventional Commit messages, and push everything automatically.

Quick Start

Use the git-maker skill to commit all current changes and push them to the remote repository.

Frequently Asked Questions about git-maker

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

FAQPage Schema
How do I automate grouping, committing, and pushing changes across multiple Git worktrees?

Yes, you can automate Conventional Commit messages for multi-repository workflows. The grouping logic automatically partitions your staged changes into logical commits per repository, ensuring strict adherence to Conventional Commit standards before pushing.

Does automated commit and push orchestration prevent force-pushing to protected branches?

You need Bash and local helper scripts to run this Git workflow automation. These scripts perform preflight inspection, commit sequencing, and automated push validation to safely orchestrate your multi-repository changes.

What's the best way to commit multiple feature changes in a monorepo with Conventional Commits?

The best way to commit monorepo changes is using automated logical grouping. The workflow partitions your changes into distinct Conventional Commits, sequences them safely, and validates the push to the remote repository in a single operation.

Why does Git commit automation fail if one commit in a sequence encounters an error?

Git commit automation fails safely because it ensures all commits succeed before any push is attempted. This strict sequencing prevents partial pushes and maintains repository integrity when errors occur during the commit phase.