commit

Commit staged code changes with conventional messages and push to remote.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Devattom/.claude --skill commit-devattom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Devattom/.claude/tree/main/skills/git-commit
Command: npx skills add https://github.com/Devattom/.claude --skill commit-devattom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of committing code changes with conventional commit messages and automatically pushing them to the remote repository.

Core Features & Use Cases

  • Automated Committing: Generates commit messages based on a defined format (type(scope): brief description).
  • Automatic Staging: Stages all changes if nothing is currently staged.
  • Automatic Pushing: Pushes the commit to the remote repository immediately after.
  • Use Case: Quickly commit and push a bug fix using the fix type, like fix(auth): resolve login redirect loop.

Quick Start

Commit all staged changes with a conventional message and push to the remote.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automatically generate conventional commit messages and push to a remote repository?

You can automate committing and pushing by generating standardized conventional commit messages in the format `type(scope): brief description` and immediately pushing the changes to your remote repository.

What is the conventional commit format used for git version control updates?

The conventional commit format structures git version control messages as `type(scope): brief description`, such as `fix(auth): resolve login redirect loop`, ensuring consistent and readable development workflow updates.

How do I commit and push unstaged changes without manually staging files?

To commit unstaged changes without manual staging, the process automatically stages all current changes if nothing is currently staged, creates the commit, and then pushes it to the remote repository.

Do I need Git command-line tools to automate committing and pushing code?

Yes, you need Git command-line tools installed in your environment to manage staged and unstaged changes, create commits with conventional messages, and perform remote pushes automatically.

What's the best way to quickly commit a bug fix and push it to version control?

The best way to quickly commit a bug fix is using the `fix` type in a conventional commit message, like `fix(auth): resolve login redirect loop`, which automatically stages, commits, and pushes the update.

Can I push commits to a remote repository immediately after creating them?

Yes, you can push commits to a remote repository immediately after creating them, as the automated workflow handles staging, commits with conventional messages, and remote pushes in one sequence.