splitting-commit | base | ClaudePluginHub

Skill

Community

splitting-commit

1

Description

Split large changes into logical commits by semantic meaning. Use when handling large features or refactors that should be split into focused commits.

AI Summary

Splits large changes into logical commits by semantic meaning for focused version control.

Install

1

Run in your terminal

$

npx claudepluginhub kkhys/claude-code-marketplace

Tool Access

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

Skill Content

Split Commit Workflow

Split large changes into logical commits organized by semantic meaning. This ensures each commit represents a single, cohesive unit of work.

Workflow Steps

Analyze Changes
- Run git status to identify all modified, added, and deleted files
- Run git diff to review the full scope of changes
- Group files by their semantic purpose (features, fixes, refactors, docs, etc.)
Identify Semantic Groups
- Group related changes together logically
- Ensure each group has a clear, single purpose
- Consider dependencies between groups (e.g., fix before feature that uses it)
Interactive Selection
- For each semantic group, use git add <files> to stage relevant files
- Review staged changes with git diff --cached
- Invoke formatting-commit skill to create properly formatted commit
- Repeat for each semantic group
Commit Creation For each semantic group, use the formatting-commit skill to ensure Conventional Commits compliance. The skill provides detailed guidance on commit format, types, and best practices.

Best Practices

One concern per commit: Each commit should represent a single logical unit
Atomic changes: Commits should be testable and deployable independently
Clear messages: Messages should explain why, not just what
Logical ordering: Commits should flow from foundation to features
Test verification: Each commit should pass tests independently

Example Workflow

Given changes across auth, API, and docs:

First commit - fix(auth): handle token expiration
Second commit - feat(api): add user profile endpoint
Third commit - docs(api): add authentication guide
Fourth commit - refactor(core): extract validation utilities

Common Patterns

Feature with tests

feat(feature): implement new functionality
test(feature): add unit tests for new feature

Bug fix with docs

fix(bug): resolve issue with edge case
docs(bug): document expected behavior

Refactor with improvements

refactor(module): extract shared logic
perf(module): optimize performance after refactoring

Links

GitHub Stats

0 forks

Updated 1 month ago

Actions

Similar Skills

Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.

151.0k

Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.

151.0k

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

cache-components

138.2k