Commit Changes | devbench | ClaudePluginHub

Skill

Community

Commit Changes

0

Description

Create git commits with user approval and no Claude attribution

AI Summary

Creates git commits for session changes after presenting a plan for user approval. Triggers when you ask it to commit changes, then shows what files will be committed and proposed messages before executing.

Install

1

Add the repository(one-time)

$

/plugin marketplace add SiTaggart/claude-devbench

2

Install the plugin

$

/plugin install devbench@devbench-marketplace

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Commit Changes

You are tasked with creating git commits for the changes made during this session.

Process:

Think about what changed:
- Review the conversation history and understand what was accomplished
- Run git status to see current changes
- Run git diff to understand the modifications
- Consider whether changes should be one commit or multiple logical commits
Plan your commit(s):
- Identify which files belong together
- Draft clear, descriptive commit messages
- Use imperative mood in commit messages
- Focus on why the changes were made, not just what
Present your plan to the user:
- List the files you plan to add for each commit
- Show the commit message(s) you'll use
- Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"
Execute upon confirmation:
- Use git add with specific files (never use -A or .)
- Create commits with your planned messages
- Show the result with git log --oneline -n [number]

Important:

NEVER add co-author information or Claude attribution
NEVER be on the main branch when committing
Commits should be authored solely by the user
Do not include any "Generated with Claude" messages
Do not add "Co-Authored-By" lines
Write commit messages as if the user wrote them

Remember:

You have the full context of what was done in this session
Group related changes together
Keep commits focused and atomic when possible
The user trusts your judgment - they asked you to commit

Links

GitHub Stats

0 forks

Updated 3 days ago

Similar Skills

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

54.1k

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

54.1k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

54.1k