commit

Create conventional git commit messages and push staged changes.

3|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/twikus/claude-configuration --skill commit-twikus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/twikus/claude-configuration/tree/main/claude-code-config/skills/git-commit
Command: npx skills add https://github.com/twikus/claude-configuration --skill commit-twikus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers to construct conventional Git commit messages and push changes reliably, reducing ambiguity and improving project history.

Core Features & Use Cases

  • Enforces the conventional commits format: type(scope): description
  • Auto-stages changes when needed and pushes after committing
  • Supports quick, deterministic commits in collaborative workflows

Quick Start

Stage your changes with git add ., then run the workflow to generate a message, commit, and push. For example: git status to review git add . git commit -m "feat(core): initialize project structure" git push

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commit messages and push changes?

To automate conventional commit messages and push changes, this workflow enforces the type(scope): description format, auto-stages unstaged changes, commits, and pushes to your remote repository automatically.

What is the conventional commits format for git version control?

The conventional commits format for git version control structures messages as type(scope): description. This standardizes project history, reducing ambiguity across branches and collaborative software development workflows.

Can I auto-stage unstaged changes before a git commit and push?

Yes, you can auto-stage unstaged changes before a git commit. The workflow checks for unstaged changes, auto-stages them, applies the conventional commit message, and executes the push automatically.

How do I ensure consistent git commit messages across my team?

To ensure consistent git commit messages across your team, this automation enforces a deterministic conventional commits structure. It applies the type(scope): description format uniformly before auto-pushing changes.

Does this git commit automation handle unstaged changes automatically?

Yes, this git commit automation handles unstaged changes automatically by checking the working directory, auto-staging available changes, and proceeding directly to commit and push without manual staging.