signal-commit

Generate and execute Conventional Commits from staged diffs.

10|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mattbaconz/signal --skill signal-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-commit
Source: https://github.com/mattbaconz/signal/tree/main/gemini-signal/skills/signal-commit
Command: npx skills add https://github.com/mattbaconz/signal --skill signal-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Stage changes and create a conventional commit with zero prompts, enabling fast, consistent version control workflows.

Core Features & Use Cases

  • Conventional commits: generate type(scope): description messages automatically from diffs.
  • Atomic commits: support for --split to create per-logical-change commits.
  • One-turn execution: perform git diff, add, and commit in a single streamlined action.

Quick Start

Run /signal-commit to generate and apply a conventional commit for your staged and unstaged changes.

Frequently Asked Questions about signal-commit

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

FAQPage Schema
How do I automate git commits with conventional commit messages from staged diffs?

You can automate git commits by running a command that analyzes your staged diff and generates a conventional commit message automatically. This performs the diff, add, and commit actions in a single step with zero prompts.

What is the conventional commits format for automated git workflow messages?

Conventional commits format structures git messages as type(scope): description, enforcing a maximum of 72 characters for the description. It generates the appropriate type and scope automatically based on the code changes in your diff.

Can I split a staged diff into multiple atomic commits for separate logical changes?

Yes, you can split a staged diff into atomic commits by using the split mode. This feature creates a separate commit for each logical change within your diff, ensuring your version control history remains clean and isolated.

How do I preview a conventional commit message before applying it to my repository?

You can preview a conventional commit message before applying it by using the dry run mode. This generates the commit message from your staged changes without actually executing the commit, allowing you to review the output safely.

Does this automation tool support pushing commits to a remote repository automatically?

Yes, the automation tool supports pushing commits directly to a remote repository by using the push mode. This executes the diff, add, commit, and push actions seamlessly in a single streamlined workflow operation.

Do I need any external dependencies to generate conventional commits from git diffs?

No external dependencies are required to generate conventional commits from git diffs. The tool operates independently using its internal scripts to analyze changes and execute the commit workflow without additional packages.