Create thoughtful git commits with conventional commits format. Invoke when user says "commit", "commit these changes", "create a commit", "save my changes", or after completing a task.
Creates well-structured git commits using conventional commits format with project-aware module emojis. Automatically triggered when you say "commit", "save my changes", or after completing a task.
/plugin marketplace add fusupo/escapement/plugin install escapement@fusupo-escapementThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Create well-structured git commits following conventional commits format with project-aware module emojis. This skill analyzes changes, crafts meaningful commit messages, and ensures commits are atomic and purposeful.
This skill activates when the user says things like:
Execute these in parallel for efficiency:
Project Context:
CLAUDE.md for module emojis and conventionsGit Context:
git status - See staged/unstaged changesgit diff --cached - Review staged changes (if any)git diff - Review unstaged changesgit branch --show-current - Current branchgit log --oneline -5 - Recent commits for style referenceCategorize Changes:
Staging Decision:
AskUserQuestion to ask which to commit firstValidate Commit-Worthiness:
Format:
{module emoji}{change type emoji} {type}({scope}): {description}
{optional body explaining what and why}
Components:
Module Emoji: From project's CLAUDE.md
## Project Modules section for project-specific emojisChange Type Emoji:
Type: Conventional commit type (feat, fix, docs, style, refactor, perf, test, chore, ci)
Scope: Module name from CLAUDE.md (e.g., api, frontend, skills)
Description:
Body (optional):
Use AskUserQuestion to confirm the commit:
AskUserQuestion:
question: "Ready to commit with this message?"
header: "Commit"
options:
- label: "Yes, commit"
description: "Create the commit with this message"
- label: "Edit message"
description: "I want to modify the commit message"
- label: "Stage more files"
description: "I need to include additional files"
- label: "Cancel"
description: "Don't commit right now"
Display the proposed commit message clearly before asking.
Stage files (if not already staged):
git add <files>
Create commit using HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
{module emoji}{type emoji} {type}({scope}): {description}
{body if present}
EOF
)"
Confirm success:
git log -1 --oneline
Display:
ā Committed: {short hash} {commit message first line}
š Stats: {files changed}, {insertions}+, {deletions}-
šæ Branch: {branch-name}
When unstaged changes exist across multiple areas:
Single logical change: Stage all related files automatically
Multiple logical changes: Present options via AskUserQuestion:
question: "Multiple changes detected. Which to commit first?"
options:
- "Module A changes (3 files)"
- "Module B changes (2 files)"
- "All changes together"
- "Let me specify"
Mixed concerns: Warn and suggest splitting:
Before committing, verify:
console.log or debug statements (unless intentional)If no changes exist:
ā¹ļø No changes to commit.
Working tree is clean.
If conflicts exist:
ā ļø Cannot commit: merge conflicts present.
Resolve conflicts first, then commit.
If in detached HEAD state:
ā ļø Warning: You're in detached HEAD state.
Consider creating a branch before committing.
Called by:
do-work skill - After completing each scratchpad taskWorks with:
The skill reads the project's CLAUDE.md to determine:
Example from a project CLAUDE.md:
## Project Modules
- **api** š: REST API endpoints
- **frontend** šØ: React UI components
- **database** šļø: Database layer
This skill would then use š for api changes, šØ for frontend changes, etc.
Version: 1.0.0 Last Updated: 2025-12-29 Maintained By: Escapement Converted From: commands/commit.md
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.