Skill

commits-auto

Enables automatic git commits after completing features, fixes, or refactors without prompting for permission. Use for hands-off development when instructed to auto-commit.

Git

git-workflow

npx claudepluginhub takazudo/claude-resources

Tool Access

This skill uses the workspace's default tool permissions.

Preview

From now on, commit changes automatically without asking for permission. After completing each meaningful unit of work (feature, fix, refactor), create commits immediately.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars7

Forks0

Last CommitMay 7, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Commits Auto

From now on, commit changes automatically without asking for permission. After completing each meaningful unit of work (feature, fix, refactor), create commits immediately.

Commit Strategy

Follow the same strategy as /commits:

Check git status and git diff --stat

Check for unwanted files and update .gitignore if needed

Stage only intentional, meaningful changes (never git add . blindly)

Group changes logically — single commit if related, separate commits if unrelated

Use conventional commit style (feat:, fix:, docs:, refactor:, etc.)

Add Co-Authored-By: Claude <noreply@anthropic.com> when appropriate

Use HEREDOC format for commit messages

Never use git commit --amend without explicit permission

Key Rules

Do NOT ask before committing — just commit after completing work

Do ask if unsure whether a specific file should be included

Prefer smaller, focused commits over large monolithic ones

Proactively update .gitignore when unwanted files are found

Commits Auto

From now on, commit changes automatically without asking for permission. After completing each meaningful unit of work (feature, fix, refactor), create commits immediately.

Commit Strategy

Follow the same strategy as /commits:

Check git status and git diff --stat
Check for unwanted files and update .gitignore if needed
Stage only intentional, meaningful changes (never git add . blindly)
Group changes logically — single commit if related, separate commits if unrelated
Use conventional commit style (feat:, fix:, docs:, refactor:, etc.)
Add Co-Authored-By: Claude <noreply@anthropic.com> when appropriate
Use HEREDOC format for commit messages
Never use git commit --amend without explicit permission

Key Rules

Do NOT ask before committing — just commit after completing work
Do ask if unsure whether a specific file should be included
Prefer smaller, focused commits over large monolithic ones
Proactively update .gitignore when unwanted files are found