domains / families / software-engineering / commit

commit

combined

Stage, commit, create PR, and merge to main. Use for the standard commit-PR-merge cycle. Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.

When to use

• 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`.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Direct-to-main instructions remain subordinate to server-side branch protection and required checks.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The three copies overlap on the core task of creating a git commit, but they diverge on scope and constraints. getsentry/skills is a focused, Sentry-specific conventional-commit procedure. sickn33/agentic-awesome-skills is also Sentry-specific but adds branch-protection policy, AI attribution rules, and a broader set of examples. brycewang-stanford/Auto-Empirical-Research-Skills is a generic commit-PR-merge workflow that does not use Sentry conventions and includes PR creation and merge steps the others lack. Crowning one would hide the alternative generic workflow and the extra Sentry constraints.