commit

Generate poetic git commit messages with staged file selection.

11|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/shannonshell/shannon --skill commit-shannonshell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/shannonshell/shannon/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/shannonshell/shannon --skill commit-shannonshell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many commits get bland, uninformative messages or take extra time to craft a clear summary and context. This Skill automates writing accurate, concise titles and short poetic bodies that describe changes clearly while adding character, reducing the friction of composing commit messages and ensuring relevant files are staged.

Core Features & Use Cases

  • Structured commit format: Produces a short imperative title (50 chars max) and a 2-8 line poetic body that accurately describes the change.
  • Targeted staging: When given a target, stages only files related to that scope; if no target is provided, stages all uncommitted changes.
  • Style guidance: Chooses an appropriate poetic form (haiku, limerick, couplet, free verse) and follows rules to favor accuracy, brevity, and tasteful humor.
  • When to use: Ideal for feature work, bug fixes, and refactors where a memorable, descriptive commit message is desired.
  • When NOT to use: Not suitable for merge commits, reverts, version bumps, or critical security fixes where conventional messages are preferred.

Quick Start

Ask the assistant: /commit fix login crash to stage the related files and generate a concise title plus a short poetic commit body.

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?

To automate git commit messages, this tool stages targeted or all uncommitted files and generates a concise 50-character title with a 2-8 line poetic body. It integrates directly with git to diff, stage, and commit changes accurately.

Can I generate poetic commit messages for specific files only?

Yes, you can generate poetic commit messages for specific files by providing a target scope. The tool stages only the files relevant to your specified target, or it stages all uncommitted changes if no target is given.

What is the best way to write descriptive git commit messages for refactors?

The best way to write descriptive git commit messages for refactors is using an automated tool that applies a structured format. It produces a short imperative title and a 2-8 line poetic body, favoring accuracy, brevity, and tasteful humor.

When should I not use automated commit message generation?

You should not use automated commit message generation for merge commits, reverts, version bumps, or critical security fixes. These scenarios require conventional messages where standard格式 is preferred over poetic descriptions.