commit vs internal-comms
Side-by-side comparison of two Claude Agent Skills. Pick the right one for Claude Code or Claude Desktop.
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional com
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever
Comparison
| Feature | commit | internal-comms |
|---|---|---|
| Bundled scripts | no | no |
| Allowed tools | any | any |
| Install scope | personal | personal |
| Category | coding | writing |
| Verified | ||
| License | — | Complete terms in LICENSE.txt |
| Author | Sentry | Anthropic |
| Repo | getsentry/skills | anthropics/skills |
When to pick commit
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.
When to pick internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Looking for something else? Browse all skills.