commit

Automate pre-commit quality gates and conventional commit workflows for Git projects.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/89jobrien/dotfiles --skill commit-89jobrien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/89jobrien/dotfiles/tree/main/dot-claude/skills/commit
Command: npx skills add https://github.com/89jobrien/dotfiles --skill commit-89jobrien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates pre-commit quality checks and the entire commit workflow, eliminating manual steps and ensuring consistent, clean commits.

Core Features & Use Cases

  • Run pre-commit quality gates (fmt, clippy, tests) before staging changes.
  • Write and enforce a conventional commit message, including Co-Authored-By trailers.
  • Push to the current branch with a clear, standardized history.

Quick Start

Execute the commit workflow to automatically run pre-commit checks, stage changes, and push with a conventional message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate pre-commit quality checks for a Rust project?

Automating pre-commit checks for a Rust project involves running quality gates like fmt, clippy, and tests before staging changes to ensure code style and validity. This process eliminates manual steps by validating every commit automatically.

How do I enforce conventional commit messages with Co-Authored-By trailers?

Enforcing conventional commit messages with Co-Authored-By trailers requires automating the commit workflow to write and apply standardized messages. This ensures every push to a branch maintains a clear, properly formatted history without manual input.

Can I use pre-commit hooks to run cargo fmt and clippy before staging?

Yes, you can use pre-commit hooks to run cargo fmt and clippy before staging changes. This setup applies quality gates to Rust projects, ensuring that style and linting checks pass successfully before changes are staged and committed.

What is the best way to automate git commit and push workflows?

The best way to automate git commit and push workflows is to execute an automated workflow that runs pre-commit checks, stages validated changes, and pushes to the current branch with a conventional commit message and author trailers.

Does this conventional commit workflow work with non-Rust Git projects?

Yes, the conventional commit workflow applies to Rust and other Git-enabled projects. It uses cargo and pre-commit hooks to enforce style, tests, and standardized messages across any supported Git repository environment.