commit

Enforce standardized commit messages and pre-commit quality checks via git workflows.

3|1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/sirius-cc-wu/sirius-skills --skill commit-sirius-cc-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/sirius-cc-wu/sirius-skills/tree/main/commit
Command: npx skills add https://github.com/sirius-cc-wu/sirius-skills --skill commit-sirius-cc-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically enforce consistent, high-quality commits by validating staged changes, escaping backticks, and ensuring code quality through verification steps.

Core Features & Use Cases

  • Staged Change Verification: Review exactly what is staged with the git status command and the diff of staged changes to ensure only relevant changes are included.
  • Quality Assurance: Run build checks and tests to maintain code quality and prevent regressions.
  • Commit Message Crafting: Enforce the [Scope/ID]: [summary] format, extract scope from the branch name, and ensure the body content avoids unsafe characters.
  • Safe Commit Execution: Use a file-based commit message with git commit -F to safely handle multi-line messages; avoid inline -m when the body may contain complex content.
  • Operational Best Practices: Provide guidance on creating and applying robust commit messages and handling edge cases.

Quick Start

Follow the steps to verify changes, run QA, and commit with a properly formatted message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce a standardized git commit message format across my repository?

To enforce a standardized git commit message format, you validate staged changes and apply the [Scope/ID]: [summary] structure. This approach automatically extracts the scope from the branch name while ensuring the body content avoids unsafe character sequences.

What is the best way to safely commit multi-line git messages with backticks?

The best way to safely commit multi-line git messages with backticks is using a file-based commit message with git commit -F. This method safely handles complex content and encoding requirements while bypassing the limitations of inline -m flags.

How do I run pre-commit quality checks on staged changes before executing git commit?

To run pre-commit quality checks on staged changes, review the git status and staged diff to verify included files, then execute build checks and tests. This maintains code quality and prevents regressions before the final commit execution.

Does this commit workflow support extracting scope automatically from the branch name?

Yes, this commit workflow supports extracting scope automatically from the branch name. It uses the extracted text to construct the standardized [Scope/ID]: [summary] commit message format required by the repository rules.

Why should I avoid inline -m flags when committing complex multi-line messages?

You should avoid inline -m flags when committing complex multi-line messages because they fail to safely handle backticks and encoding requirements. Using git commit -F with a file-based message ensures safe execution of complex body content without shell escaping errors.