commit-staged

Create conventional commit messages from staged Git changes.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/TophC7/Sworm --skill commit-staged-tophc7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-staged
Source: https://github.com/TophC7/Sworm/tree/main/.claude/skills/commit-staged
Command: npx skills add https://github.com/TophC7/Sworm --skill commit-staged-tophc7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a conventional commit from the currently staged changes in a Git working tree, allowing you to preserve a clean, standardized history without editing files.

Core Features & Use Cases

  • Inspects staged changes and validates that something is staged before proceeding.
  • Drafts a conventional commit message from the diff, including an optional scope and a concise summary.
  • Executes the commit via a controlled heredoc, stops immediately on failure, and reports the resulting commit hash when successful.
  • Supports common workflows across any Git repository to maintain consistent history.

Quick Start

Tell me to commit the currently staged changes using a conventional commit message.

Frequently Asked Questions about commit-staged

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

FAQPage Schema
How do I automate a conventional commit message from staged Git changes?

To automate a conventional commit message from staged Git changes, the skill inspects the current diff, drafts a standardized message with a type and scope, and executes the commit via a safe heredoc. It validates the diff first and stops immediately on failure to prevent inconsistent history.

What is the best way to ensure my Git commit history follows conventional commits?

The best way to ensure Git commit history follows conventional commits is to automate message drafting directly from the staged diff. This skill generates a standardized type, optional scope, and concise summary, executing the commit safely without manual file editing.

Does this conventional commit automation work with any Git repository workflow?

Yes, this conventional commit automation supports common workflows across any Git repository. It requires only staged changes in the working tree, validates the diff, and maintains consistent history regardless of the specific project setup.

How do I commit only staged changes without manually writing a commit message?

To commit only staged changes without manual writing, instruct the skill to process the working tree. It validates the staged diff, drafts a conventional commit message, executes via a controlled heredoc, and reports the resulting commit hash upon success.

What happens if a conventional commit fails during execution?

If a conventional commit fails during execution, the skill stops immediately to prevent inconsistent history. It uses a controlled heredoc for the commit process and only reports the resulting commit hash when the operation is successful.