skills.rest
AmidVoshakul
AmidVoshakulCOMMUNITY
Explore all skills by this author →
GitHub

commit

Create conventional git commit messages with issue references and branch safety checks.

Updated Dec 29, 2025
Search Tags:#git#version control#workflow automation#commit#conventional commits#sentry
One-click install
npx skills add https://github.com/AmidVoshakul/chatorai --skill commit-amidvoshakul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/AmidVoshakul/chatorai/tree/main/assets/skills/commit
Command: npx skills add https://github.com/AmidVoshakul/chatorai --skill commit-amidvoshakul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent commit messages and prevents accidental commits to protected branches by enforcing strict conventional commit formatting and branch safety checks.

Core Features & Use Cases

  • Conventional Commit Enforcement: Automatically structures messages using Sentry-approved types, scopes, and issue references.
  • Branch Safety: Validates the current branch and mandates the creation of feature branches before committing to main or master.
  • Use Case: When finishing a feature, use this skill to generate a properly formatted commit message that links to a specific issue tracker ID while ensuring the code is safely isolated on a feature branch.

Quick Start

Use the commit skill to save my current changes with a descriptive message following the conventional commit format.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce conventional commit formatting for git commits?▼

This skill standardizes git commit messages by applying Sentry-approved conventional commit structures and mandatory issue tracker references to ensure commit history hygiene.

How do I prevent accidental commits to protected git branches?▼

To prevent accidental commits to protected branches, the workflow validates the current branch status and mandates the creation of a feature branch before committing to main or master.

Can I link conventional commit messages to an issue tracking system?▼

Yes, you can link conventional commit messages to an issue tracking system by generating a properly formatted commit message that includes a specific issue tracker ID.

Do I need git CLI access to automate conventional commit workflows?▼

Yes, automating conventional commit workflows requires git CLI access to verify the current branch status and perform the commit operations.

What is the best way to standardize git commit history with Sentry conventions?▼

The best way to standardize git commit history is to enforce strict conventional commit formatting with Sentry-approved types and scopes while running branch safety checks before each commit operation.

Why does my workflow automation require a feature branch before committing to main?▼

Your workflow automation requires a feature branch to ensure code isolation and branch safety, preventing accidental commits to protected branches like main or master.

Related Skills

Explore More Software Engineering Skills→
ReScienceLabReScienceLab
10

using-git-worktrees

Create an isolated git worktree for a feature branch with automatic project setup.

Official
Advanced
vankichivankichi

commit-push-branch

Create branches, commit changes, and push to a Git remote repository.

Community
Intermediate
sangrokjungsangrokjung
1

fix

Automates lint error fixes and formatting enforcement via yarn linc and prettier scripts.

Community
Basic
ANcpLuaANcpLua
5

smart-commit

Generate conventional commit messages from staged changes with type, scope, and issue references.

Community
Basic