commit-v2

name	commit-v2
description	Sentry Commit Messages workflow skill. Use this skill when the user needs ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
version	0.0.1
category	development
tags	["commit-v2","commit","always","use","committing","changes","never","directly"]
complexity	intermediate
risk	caution
tools	["codex-cli","claude-code","cursor","gemini-cli","opencode"]
source	community
author	sickn33
date_added	2026-04-16
date_updated	2026-04-25

Sentry Commit Messages

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/commit from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Sentry Commit Messages Follow these conventions when creating commits for Sentry projects.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Format, Commit Types, AI-Generated Changes, Revert Format, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• The user asks to commit code, prepare a commit message, or save changes in git.
• You need Sentry-style commit formatting with conventional commit structure and issue references.
• The task requires enforcing branch safety before committing, especially avoiding direct commits on main or master.
• Use when the request clearly matches the imported source intent: ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit,....
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Situation	Start here	Why it matters
First-time use	metadata.json	Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review	ORIGIN.md	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	SKILL.md