skills.rest
lvstb
lvstbCOMMUNITY
Explore all skills by this author →
GitHub

auto-commit

Commit code changes after each completed task using conventional commit messages.

Updated Dec 22, 2024
Search Tags:#git#workflow#development#version control#commit#auditing
One-click install
npx skills add https://github.com/lvstb/nix-config --skill auto-commit-lvstb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-commit
Source: https://github.com/lvstb/nix-config/tree/main/home/opencode/skills/auto-commit
Command: npx skills add https://github.com/lvstb/nix-config --skill auto-commit-lvstb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that every discrete unit of work is captured as a separate commit in the git history, providing a clear, step-by-step audit trail of the agent's progress.

Core Features & Use Cases

  • Granular Committing: Commits code changes immediately after each completed task, rather than batching them.
  • Detailed History: Creates a commit for every feature, bug fix, or planned step, making it easy to review and revert specific changes.
  • Use Case: When implementing a new user authentication module, each sub-task (e.g., setting up the database schema, creating the login API endpoint, implementing password hashing) will be a separate, clearly described commit.

Quick Start

Commit the changes made during the last completed task using a descriptive message.

Frequently Asked Questions about auto-commit

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

FAQPage Schema
How do I automate git commits after every development task?▼

To automate git commits after every task, this Skill enforces a strict workflow that commits code changes immediately upon completion. It ensures every feature or bug fix is captured as a separate commit in the repository history.

What is granular committing and how does it create a detailed git history?▼

Granular committing captures each sub-task, such as setting up a database schema or creating an API endpoint, as a separate commit. This creates a detailed git history that provides a clear audit trail of development progress.

How do I format commit messages for automated task workflows?▼

To format commit messages for automated workflows, you must adhere to conventional commit message formats. This requirement ensures clear, actionable history tracking for every code change made during multi-step development processes.

Does this automated commit workflow apply to multi-step bug fixing and plan execution?▼

Yes, this automated commit workflow applies to multi-step bug fixing and plan execution within a git repository. It triggers commits immediately after each planned step is completed, regardless of the specific development task type.

Why should I commit after every task instead of batching code changes?▼

Committing after every task instead of batching code changes makes it easy to review and revert specific changes. Granular commits provide a clear audit trail of progress, ensuring that discrete units of work are tracked individually.

Related Skills

Explore More Software Engineering Skills→
eavichayeavichay

git-commit

Stage and commit repository changes after Spec Kit lifecycle events.

Community
Intermediate
bswrundquistbswrundquist

commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Community
Basic
ReidondReidond

commit-message

Generate conventional commit messages from staged diff analysis.

Community
Intermediate
yoshihiko555yoshihiko555

commit

Stage and commit only files discussed in the conversation.

Community
Advanced