commit

Create formatted git commits for staged changes with safety rules.

1.3k|179|Updated Jul 28, 2025
One-click install
npx skills add https://github.com/openonion/connectonion --skill commit-openonion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/openonion/connectonion/tree/main/connectonion/cli/co_ai/skills/builtin/commit
Command: npx skills add https://github.com/openonion/connectonion --skill commit-openonion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating consistent, well-formatted git commits that explain why changes were made, improving project history readability.

Core Features & Use Cases

  • Gather repository state and changes (git status, git diff --staged, git log) to determine the scope of a commit.
  • Draft meaningful commit messages that emphasize rationale and impact, not just what changed.
  • Execute commits with safeguards to avoid committing sensitive files and to follow established conventions.

Quick Start

Provide a concise commit message for the staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit messages for staged changes?

You can automate git commit messages by gathering git status, staged diffs, and log data to draft meaningful messages that emphasize rationale and impact. This ensures consistent project history readability without manual message drafting.

What makes a well-formatted git commit message for version control?

A well-formatted git commit message emphasizes why changes were made rather than just listing what changed. It follows established conventions and includes clear rationale derived from analyzing the staged git diff and repository context.

Can I automatically avoid committing sensitive files in my git workflow?

Yes, automated git commit workflows can enforce safety rules to detect and avoid committing sensitive files. This safeguard operates while gathering repository state and executing the final commit for your staged changes.

Does automated commit message generation work with existing git log conventions?

Automated commit message generation works with existing conventions by collecting git log data to match your repository's established style. It analyzes prior history to ensure newly drafted messages align with your project's formatting patterns.

What is the best way to write consistent git commit messages across a development team?

The best way to write consistent git commit messages is to automate the drafting process based on staged diffs and repository history. This removes subjective writing variations and enforces safety rules for sensitive files across all team commits.