commit

Name: commit
Availability: InStock
Author: Avvale

Generate conventional commit messages and run git add, commit, and push.

1|Updated Jun 20, 2022

Search Tags:#git #workflow #commit #code-quality #version-control #conventional-commits

Ready to run

npx skills add https://github.com/avvale/aurora-front --skill commit-avvale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/avvale/aurora-front/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/avvale/aurora-front --skill commit-avvale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and automates the creation of conventional commit messages, ensuring consistent history and cleaner PR reviews.

Core Features & Use Cases

Evaluate changes: analyze git status, diffs and recent commits to decide an appropriate type and scope.
Generate conventional commit message: propose a message following the Conventional Commits spec.
Stage and commit: perform git add and git commit with proper message.
Push to remote: push to the current branch, set upstream if needed.
Verification: show the latest commit and status.

Quick Start

Use the commit skill after you have changed files. Steps: Run /commit, the system will analyze via git status, diff, diff --staged, etc. Then confirm, generate message, stage, commit, push. Then show status.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate conventional commit messages for git changes automatically?▼

To generate conventional commit messages automatically, you run the commit command after changing files. The system analyzes git status and diffs to deduce the correct type and scope, then proposes a syntax-compliant message for you to confirm.

What is the best way to automate staging, committing, and pushing in a Git workflow?▼

Automating staging, committing, and pushing in a Git workflow is handled by evaluating your code diffs to generate a conventional message, executing git add and git commit deterministically, and pushing to your current remote branch with upstream tracking.

Does the conventional commit generation work with both small fixes and large feature updates?▼

Yes, conventional commit generation works with both small fixes and large feature updates. It analyzes recent commits and current diffs to decide an appropriate type and scope, ensuring consistent history and cleaner PR reviews across any size of code changes.

How do I ensure my git commit history follows the Conventional Commits specification?▼

To ensure your git commit history follows the Conventional Commits specification, the system applies type and scope deduction to your code changes. It proposes a compliant message and provides deterministic git commands to stage, commit, and push the update.

Can I set upstream and push to a remote branch automatically after committing?▼

Yes, you can set upstream and push to a remote branch automatically after committing. The workflow stages your files, commits with a generated conventional message, and pushes to the current branch, setting upstream if needed, followed by a status verification.