skills.rest
sasamuku
sasamukuCOMMUNITY
Explore all skills by this author →
Website𝕏@sasamukuGitHub

squash-commits

Organize git commits into appropriate granularity through manual or automated review.

8|Updated Oct 26, 2025
Search Tags:#git#code review#code maintainability#commit management#commit reorganization
One-click install
npx skills add https://github.com/sasamuku/dotfiles --skill squash-commits-sasamuku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: squash-commits
Source: https://github.com/sasamuku/dotfiles/tree/main/.claude/skills/squash-commits
Command: npx skills add https://github.com/sasamuku/dotfiles --skill squash-commits-sasamuku

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of organizing commit granularity, making the git history cleaner and more logical.

Core Features & Use Cases

  • Commit Analysis: Reviews all commits and working changes, ensuring appropriate granularity.
  • Manual Review: Offers a manual process to analyze and decide on commit granularity.
  • Automated Reorganization: Allows users to automatically reorganize commits for better readability.
  • Use Case: Ideal for developers who wish to maintain a clear and concise commit history, improving the overall readability and maintenance of the codebase.

Quick Start

Activate the squash-commits skill and follow the prompts to organize your git history into the appropriate commit granularity.

Frequently Asked Questions about squash-commits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reorganize my git history to maintain a clear and logical commit structure?▼

To reorganize your git history, you can review all commits and working changes to adjust them into appropriate commit granularity. This process supports both manual review and automated reorganization for better readability.

What is the best way to squash commits for code maintainability?▼

Squashing commits for code maintainability involves analyzing all working changes and organizing them into the most appropriate commit granularity. This ensures a clean and logical git history that simplifies future code review.

Can I manually review and decide on commit granularity before changing my git history?▼

Yes, you can manually review and decide on commit granularity before making changes. The process offers a manual mode to analyze your commits, ensuring you retain control over how the git history is reorganized.

Does automated commit reorganization work for existing working changes in git?▼

Automated commit reorganization works by reviewing all existing commits and working changes in your git history. It then automatically organizes these changes to achieve the most appropriate and logical commit granularity.

When do I need to reorganize commits to improve code review readability?▼

You need to reorganize commits when your git history lacks clear structure and logical granularity. This Skill simplifies organizing commit granularity, which directly improves overall codebase readability and maintenance for future reviews.

Related Skills

Explore More Software Engineering Skills→
CivicActionsCivicActions
2

organize-commits

Group unstaged changes into atomic git commits using project conventions.

Official
Intermediate
ProtagonistssProtagonistss

remote

Push and manage code across multiple git remotes with automated safety checks.

Community
Intermediate
willyu1007willyu1007

git-commit-conventions

Enforce Git commit message formats, branch naming, and pull request best practices.

Community
Basic
maggitmaggit

rebase

Plan and execute non-interactive git rebase operations with safety checks.

Community
Intermediate