commit

Plan and execute git commits with co-authorship attribution.

1|Updated Dec 17, 2025

Search Tags:#automation #git #commit #version-control #commit-messages #co-authorship

Ready to run

npx skills add https://github.com/JonnyCBB/claude-code-config --skill commit-jonnycbb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/JonnyCBB/claude-code-config/tree/main/plugins/jbb-feature-dev/skills/commit
Command: npx skills add https://github.com/JonnyCBB/claude-code-config --skill commit-jonnycbb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the planning and execution of git commits with explicit co-authorship attribution, reducing manual overhead and ensuring clear history.

Core Features & Use Cases

Structured Commit Planning: groups related changes into cohesive commits with descriptive messages.
Co-authorship Attribution: automatically includes co-authors in commit messages.
Mode Flexibility: supports INTERACTIVE and NON_INTERACTIVE flows, prompting for confirmation when appropriate.
Execution & Verification: stages changes with git add for specific files and displays commit history after execution.
Use Case: In a collaborative coding session, after implementing a feature, run this skill to produce a clean, attributed commit history.

Quick Start

Review the current changes, then tell me to proceed to create structured, co-authored commits.

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 co-authorship attribution?▼

Git commit automation with co-authorship attribution works by parsing arguments to plan commits, stage specific files, and generate imperative mood messages. It supports both interactive prompts and non-interactive automation to produce organized, attributed chunks.

What is structured commit planning for version control?▼

Structured commit planning is the process of grouping related changes into cohesive commits with descriptive messages. It reduces manual overhead by staging files precisely and ensuring a clear, attributed history for collaborative coding sessions.

How do I create git commit messages in the imperative mood?▼

Creating git commit messages in the imperative mood is handled automatically during the commit planning phase. The automation generates structured messages, applies co-authorship attribution, and displays the commit history after execution.

Can I use non-interactive automation for git commit execution?▼

Non-interactive automation for git commit execution is fully supported alongside interactive flows. You can run the commit planning process without manual confirmation prompts, allowing it to stage files and create attributed messages automatically.

Does this git commit automation require any external dependencies?▼

Git commit automation requires no external dependencies to function. It operates independently to parse arguments, plan commit chunks, stage file changes, and display the final commit logs without needing additional tool installations.