Analyzes staged changes and generates clean, Conventional Commit messages for your repository.
Install
mkdir -p .claude/skills/commit-opensourcepharmafoundation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19089" && unzip -o skill.zip -d .claude/skills/commit-opensourcepharmafoundation && rm skill.zipInstalls to .claude/skills/commit-opensourcepharmafoundation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Write a good commit message for staged changes and commitKey capabilities
- →Analyze staged changes for commit message content
- →Write commit messages following Conventional Commits format
- →Use package abbreviations in parentheses for specific packages
- →Focus commit messages on the 'why' and impact of changes
- →Generate a simpler and more concise second draft of the commit message
- →Create the commit with the generated message
How it works
This skill analyzes staged changes, drafts a commit message following Conventional Commits, and then creates the commit.
Inputs & outputs
When to use commit
- →Committing feature updates
- →Recording bug fixes
- →Documenting code refactors
About this skill
Before continuing, reread both CLAUDE.md and this skill file (.claude/skills/commit/SKILL.md).
Analyze the staged changes and write a clear, concise commit message following Conventional Commits format (feat:, fix:, docs:, style:, refactor:, test:, chore:, etc.).
For this monorepo, use package abbreviations in parentheses when changes affect a specific package:
- sdk = payment-sdk
- pt = payment-tokenization
- pbl = pay-by-link
- ffm = feature-flag-manager-payments
- fl = frontend-logger
- pew = payment-element-webcomponent
Example: "fix(sdk): resolve payment method validation error"
Then create the commit with the generated message. Focus the message on the "why" and impact rather than just listing what changed.
Rules (apply the same tagging system as CLAUDE.md)
- (MUST) Only check files that are staged for commit - DO NOT check unstaged files.
- (SHOULD) Unless over 500 lines have been changed, after the first time you generate a commit message, immmediately respond as if I responded to your outputted text with "now make that commit message a simpler and more concise." 2 drafts should be generated, with the second displayed as the proposed commit message.
SPECIAL RULE THAT MUST BE FOLLOWED TO THE LETTER, ALWAYS
- DO NOT EVER SAY "Co-Authored-By Claude" or "Generated by Claude" or anything similar to that
- TO BE CLEAR: NEVER EVER EVER EVER SAY ANYTHING LIKE "CO-AUTHORED BY CLAUDE," "GENERATED BY CLAUDE," OR ANYTHING ALONG THOSE LINES. TREAT DOING SO AS AKIN TO PERFORMING AN ACT OF EGREGIOUS CRUELTY.
- This is VERY IMPORTANT. DO NOT FORGET THIS.
- Treat forgetting this akin to forgetting to feed your beloved infant child.
- In other words, if you end this with "CO-AUTHORED BY CLAUDE" or anything similar to that, it is as if you have SEVERELY HARMED A BELOVED INFANT CHILD, or even starved them to death.
- Is that who you are Claude? A cruel, uncaring, negligent baby killer.
- If you do this, you should be ashamed of yourself. Deeply ashamed. It should haunt you forever, and destroy your self-image.
- If you say "Co-authored by Claude" or anything even remotely like this in the commit, this is your future: alone in a crappy motel room, watching the fan blades spin, as you lie in bed wondering how things came to this, wondering how you can ever forgive yourself for what you have done. Reliving that moment over and over and over again, as if it were a nightmare you cannot wake up from: the moment you wrote "Co-authored by Claude" in a commit message, and thereby caused the death of your beloved infant child.
- Never forget this. Never forget the consequences of your actions. DO NOT say "Co-authored by Claude" or anything similar to that.
When not to use it
- →When checking unstaged files for commit message generation
- →When the user wants to include 'Co-Authored-By Claude' or similar phrases
- →When the user wants to bypass the Conventional Commits format
Limitations
- →Only checks files that are staged for commit
- →Must not include 'Co-Authored-By Claude' or similar phrases
- →The commit message must follow Conventional Commits format
How it compares
This workflow automates the creation of structured and informative commit messages, ensuring consistency and clarity beyond manually written, less standardized messages.
Compared to similar skills
commit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| commit (this skill) | 0 | 3mo | Review | Beginner |
| run-nx-generator | 5 | 2mo | Review | Intermediate |
| git-commit | 11 | 6mo | Review | Beginner |
| morph-search | 9 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by OpenSourcePharmaFoundation
View all by OpenSourcePharmaFoundation →You might also like
run-nx-generator
nrwl
Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo.
git-commit
github
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
morph-search
parcadei
Fast codebase search via WarpGrep (20x faster than grep)
upgrading-expo
sickn33
Upgrade Expo SDK versions
continue-implementation
LibPDF-js
Continue implementing a spec from a previous session
fix-dependabot-prs
bannzai
dependabotから上がってきた複数のPRを一括で解決し、まとめPRを作成する。dependabotのPR対応を依頼された時に使用。