make-commit

Creates Conventional Commits from git diffs and pushes the branch to origin.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill make-commit-sagittaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-commit
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/make-commit
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill make-commit-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Writing consistent, machine-readable commit messages and deciding how to split mixed changes into logical commits is repetitive and error-prone. This Skill inspects the repository state, splits changes into logical units, writes Conventional Commits messages from the actual diff, commits them, and pushes the branch — all through guarded scripts that cannot rewrite history. ## Core Features & Use Cases - Repository preflight: Detects detached HEAD, default-branch commits, missing upstreams, and collects the scopes already used in the repository's history. - Diff-driven commit splitting: Groups staged and unstaged changes into logical units and writes one Conventional Commits message per unit, derived from the diff rather than conversation memory. - Safe commit and push: Commits via stdin-fed scripts and pushes after every commit, publishing branches without an upstream to origin; force push, amend, and hook-skipping are deliberately unsupported. - Use Case: After finishing a feature, ask the assistant to commit the work — it checks you are not on the default branch, splits the changes, writes properly formatted messages, commits each unit, and pushes the branch. ## Quick Start Ask the assistant to commit and push the current uncommitted changes in the repository.

Frequently Asked Questions about make-commit

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

FAQPage Schema
How do I write Conventional Commits messages automatically?

Invoke the skill with a request like "commit this" and it inspects the diff, splits changes into logical units, and writes a Conventional Commits message per unit. Messages follow the type(scope): description format with scopes taken from the repository's existing history.

How do I split mixed changes into multiple commits?

The skill groups unstaged changes by area and nature of change, then commits each logical unit separately with its own message. If changes are already staged, it commits exactly that selection without expanding it.

Does the skill push commits automatically?

Yes, it pushes after every commit and publishes the branch to origin when no upstream exists. Push is skipped only when the user explicitly declines it, and the skip is reported in the summary.

Can it amend commits or force push?

No. The scripts deliberately do not support --amend, force push, or hook skipping, so history only grows. Operations that rewrite history must be done outside this skill.

What happens when committing on the default branch?

The preflight script detects the default branch via the remote and the skill asks whether the work should go there directly or a new branch should be created first. In non-interactive runs it stops and reports instead of committing.

Why does the skill fail with detached HEAD?

A commit on a detached HEAD is silently lost when the branch is switched, so the preflight script reports detached=true and the skill stops. Check out a branch first, then rerun the commit.