commit

Commit staged Git changes with a confirmed message and co-author tag.

Updated Jan 19, 2016
One-click install
npx skills add https://github.com/skinnybrian/dotfiles --skill commit-skinnybrian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/skinnybrian/dotfiles/tree/main/claude/skills/commit
Command: npx skills add https://github.com/skinnybrian/dotfiles --skill commit-skinnybrian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines committing code changes by handling status checks, selective staging, clear message generation, and optional co‑author attribution while respecting pre‑commit hooks.

Core Features & Use Cases

  • Checks repository status and diffs while excluding secret files.
  • Reviews recent commit messages to maintain style consistency.
  • Generates or accepts a commit message, presents it for user confirmation.
  • Adds only the explicitly listed files (avoids blanket adds) and creates the commit with a co‑author tag.
  • Applies when developers need a reliable, repeatable commit workflow that integrates with existing Git tooling.

Quick Start

Ask the commit skill to commit my changes with the message "Fix login bug".

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit staged changes in Git with a consistent message style?

To commit staged changes with a consistent message style, the skill reviews recent commit history to match formatting. It then generates a purpose-driven message, presents it for your confirmation, and commits the selectively added files.

Can I add specific files to a Git commit without a blanket git add?

Yes, you can commit specific files without a blanket add. The skill adds only the explicitly listed files to the staging area, ensuring selective file addition and preventing accidental inclusion of unwanted changes.

How do I include a co-author in my Git commit message?

To include a co-author in your Git commit message, the skill supports optional co-author attribution. It generates the commit and automatically appends the co-author tag to the message before finalizing the changes.

Does this Git commit workflow run pre-commit hooks before finalizing changes?

Yes, this Git commit workflow respects pre-commit hooks. It checks repository status and diffs while ensuring pre-commit hook compliance before creating the actual commit with your confirmed message.

What is the best way to exclude secret files when preparing code updates for version control?

The best way to exclude secret files when preparing code updates is using a skill that checks repository status and diffs while automatically excluding secret files. This ensures sensitive data is never accidentally staged or committed.