commit

Stage and commit Git changes with a diff-derived message.

12|1|Updated Jan 16, 2024
One-click install
npx skills add https://github.com/kaosnyrb/FrankyCLI --skill commit-kaosnyrb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kaosnyrb/FrankyCLI/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/kaosnyrb/FrankyCLI --skill commit-kaosnyrb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stages all modified and untracked files and commits them with a meaningful message derived from the diff, reducing manual editing and guesswork.

Core Features & Use Cases

  • Automatically stage modified and new files before commit
  • Derive a concise, descriptive commit message from the diff to improve history readability
  • Supports standard Git workflows across short-lived and long-running branches

Quick Start

Run /commit to stage all changes and create a descriptive commit message from the diff.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a meaningful git commit message from a diff?

To generate a meaningful git commit message from a diff, the Skill inspects your working tree changes and recent log history to derive a concise, conventional subject line automatically, reducing manual editing and guesswork.

Can I automatically stage modified and untracked files before a git commit?

Yes, you can automatically stage modified and untracked files before a git commit. The Skill stages all changes from your working tree to the Git repository in a single action, supporting standard development workflows across both short-lived and long-running branches.

What is the best way to keep git history clear during daily development workflows?

The best way to keep git history clear during daily development workflows is to derive descriptive commit messages directly from the code diff. This ensures each feature addition, bug fix, or cleanup commit has a concise, meaningful subject line.

Does this automated commit workflow require any external dependencies?

No, this automated commit workflow does not require any external dependencies. It operates independently by inspecting standard git status, diff, and log outputs to stage your working tree and compose a descriptive commit message.

How do I stage and commit changes with a descriptive message in one step?

To stage and commit changes with a descriptive message in one step, you run the command. It stages all modified and new files, analyzes the resulting diff, and creates a commit with a concise, conventional subject line.