commit

Stage, commit, and push changes with conventional commit messages.

15|6|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lionbenjamin/agent-templates --skill commit-lionbenjamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/lionbenjamin/agent-templates/tree/main/skills/commit
Command: npx skills add https://github.com/lionbenjamin/agent-templates --skill commit-lionbenjamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage, commit, and push changes with conventional commit style to produce meaningful, navigable Git history.

Core Features & Use Cases

  • Atomic Changes: Ensure each commit represents a single logical change.
  • Conventional Commits: Enforce prefixes like feat:, fix:, docs:, and more for consistent histories.
  • Pre-Commit Verification: Run tests and reviews before committing to catch issues early.
  • Use Case: When implementing a feature, create a single, descriptive commit that captures the change.

Quick Start

Run the commit skill to stage changes and create conventional commits for your current branch.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commits with conventional commit prefixes?

Automate conventional commits by running the skill to stage changes and generate messages with prefixes like feat:, fix:, and docs:, ensuring a clean and navigable Git history.

What is the best way to enforce atomic changes in Git?

Enforce atomic changes by ensuring each git commit represents a single logical change, capturing the update descriptively to maintain consistent project history.

Can I run pre-commit checks and tests before pushing changes?

Yes, pre-commit verification runs tests and reviews before committing to catch issues early, ensuring code quality before changes are pushed to the repository.

Does this tool support conventional commit prefixes for release preparation?

Yes, it applies conventional commit prefixes during feature work, bug fixes, and release preparation to automate staging, committing, and pushing changes consistently.

Why should I use conventional commits for my project history?

Conventional commits produce meaningful, navigable Git history by enforcing consistent prefixes and atomic changes, making it easier to track features, fixes, and documentation updates.