Commit

What it does

This source separates branch checks, message composition and issue references. It specifies a compact subject, optional explanatory body and explicit breaking-change footer. It also calls out privacy-sensitive material that should not appear in commit messages, which remain durable repository history.

Best for

Teams already using compatible conventional commit rules that want more consistent descriptions of a narrowly scoped change.

Tradeoffs and requirements

The allowed type names, branch behavior and formatting are publisher conventions. They should be reconciled with the target repository rather than adopted automatically. A polished message does not prove that the staged files are intended or that tests passed.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/getsentry/skills/tree/d12f250460ffd961f549dbebf7eeb0cf4afd4c2e/skills/commit --skill commit

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

55/100

55

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Inspect the branch and staged diff, separate unrelated edits and establish the technical purpose. Draft a message that describes the final change, adding an issue reference only when its effect is intended.

How to judge the result

Check the resulting commit’s file list, subject and body. Confirm that references do not close the wrong issue, that no private context was included, and that the repository’s required validation was actually performed.