Commit Skill for Claude

by parcadei

Create git commits with user approval and no Claude attribution

1k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

3880

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill commit

The instruction itself

4 sections, as written by the author

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]

Generate reasoning (after each commit):
Run: bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <commit-hash> "<commit-message>"
This captures what was tried during development (build failures, fixes)
The reasoning file helps future sessions understand past decisions
Stored in .git/claude/commits/<hash>/reasoning.md

Important:

NEVER add co-author information or Claude attribution
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

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take parcadei/commit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.