Menu
Write a good commit message for staged changes and commit
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Freeze this session's state for later resumption with claude --resume
List frozen sessions and provide resume commands for all panels
ADMET prediction agent - assess absorption, distribution, metabolism, excretion, and toxicity profiles from molecular structure and physicochemical properties
Drug candidate ranking agent - multi-criteria scoring and prioritization of compounds for Oral Mucositis treatment
Clinical feasibility assessment agent - evaluate practical development pathways, regulatory strategy, cost estimates, and real-world viability for drug candidates
Combination therapy design agent - rational multi-compound strategy design, synergy assessment, and Ayurvedic formulation evaluation
| name | commit |
| description | Write a good commit message for staged changes and commit |
| when_to_use | When committing staged changes with an auto-generated conventional commit message |
| allowed-tools | Bash(git add:*), Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git commit:*) |
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:
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.