sase_git_commit

Enforce conventional commit headers and manage staging, validation, and rebase conflicts.

5|Updated Dec 6, 2021
One-click install
npx skills add https://github.com/bbugyi200/dotfiles --skill sase-git-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sase_git_commit
Source: https://github.com/bbugyi200/dotfiles/tree/main/home/dot_codex/skills/sase_git_commit
Command: npx skills add https://github.com/bbugyi200/dotfiles --skill sase-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces strict conventional commit standards and ensures that all git operations are properly recorded, tracked, and integrated with automated release tooling.

Core Features & Use Cases

  • Conventional Commit Enforcement: Automatically validates commit messages against semantic versioning tags like feat, fix, and chore.
  • Automated Workflow Integration: Handles complex git operations including staging, committing, and rebase conflict resolution while maintaining audit trails.
  • Use Case: Use this skill when you need to commit code changes to a repository that requires semantic versioning and automated changelog generation, ensuring your commit message follows the required header format and breaking change syntax.

Quick Start

Use the sase_git_commit skill to stage the modified files and commit them with a descriptive conventional message.

Frequently Asked Questions about sase_git_commit

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

FAQPage Schema
How do I enforce conventional commit messages in my git workflow?

Conventional commit messages are enforced by validating staged changes against semantic versioning headers like feat, fix, and chore before creating the commit. This skill automatically checks your message format and breaking change syntax to ensure compliance.

Can I automate staging and rebasing when committing code changes?

Staging and rebasing are automated by this skill through a wrapper that manages file staging, commit message validation, and rebase conflict resolution. It handles these complex git operations while maintaining audit trails for safe code integration.

Does this skill require any specific git environment setup?

A pre-configured git environment is required to use this skill, along with adherence to the SASE commit methodology for all repository modifications. You must have your repository properly initialized before executing the commit workflows.

How do I generate automated changelogs compatible with release-please?

Automated changelogs are generated by ensuring your commits use release-please compatibility through standardized conventional commit headers. The skill enforces the required semantic versioning tags so automated release tooling can parse your history correctly.

What happens if my commit message does not follow the semantic versioning format?

Commit messages that do not follow the semantic versioning format are rejected during the validation phase. The skill validates headers against tags like feat, fix, and chore, ensuring your commit is blocked before integration if it lacks proper formatting.

How do I resolve rebase conflicts during automated git commits?

Rebase conflicts are resolved by the skill's automated wrapper, which manages conflict resolution during the commit process. It facilitates safe code integration by handling the rebase operations while maintaining proper audit trails.