skills.rest
bonitasoft-presales
bonitasoft-presalesOFFICIAL
Explore all skills by this author →
GitHub

bonita-commits

Analyze and rewrite Git commit history into logical, atomic units.

Updated Jun 24, 2025
Search Tags:#git#code review#version control#commit history#rewrite#history cleanup
One-click install
npx skills add https://github.com/bonitasoft-presales/presales_workflows --skill bonita-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bonita-commits
Source: https://github.com/bonitasoft-presales/presales_workflows/tree/main/.claude/skills/bonita-commits
Command: npx skills add https://github.com/bonitasoft-presales/presales_workflows --skill bonita-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers clean up and reorganize their commit history to improve clarity, consistency, and adherence to project conventions.

Core Features & Use Cases

  • Analyzing commits to identify related changes and categorize them by purpose.
  • Proposing logical reorganization by grouping commits into meaningful units such as features, fixes, or refactoring.
  • Rewriting history to squash or reorder commits, making the history easier to understand and review.
  • Use Case: Before merging a feature branch, tidy up the commit log to clearly reflect the development process for reviewers and future references.

Quick Start

Use the bonita-commits skill to analyze your current branch and rewrite the commit history into logical, coherent units.

Frequently Asked Questions about bonita-commits

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

FAQPage Schema
How do I clean up my Git commit history before merging a feature branch?▼

To clean up Git commit history, you can analyze related changes and rewrite commits by squashing or reordering them into logical, atomic units for clearer project tracking and review.

What is the best way to organize complex commit logs for code review?▼

The best way to organize complex commit logs is to group commits by purpose, categorizing them into features, fixes, or refactoring units to ensure adherence to project conventions and message standards.

Can I rewrite Git history to squash and reorder commits in collaborative environments?▼

Yes, you can rewrite Git history to squash or reorder commits in collaborative environments, making the development process easier to understand and review before finalizing the branch.

Does this Git history cleanup approach require specific version control tools?▼

No specific version control tools are required beyond a standard Git environment, as the process analyzes your current branch and proposes a logical reorganization directly within your existing workflow.

When should I reorganize commit messages to follow best practices?▼

You should reorganize commit messages to follow best practices before merging a feature branch, ensuring the log clearly reflects the development process for reviewers and future references.

Why does my commit history need to be split into atomic units?▼

Your commit history needs atomic units to improve clarity and consistency, allowing reviewers to easily track logical changes and verify that commits follow project conventions.

Related Skills

Explore More Software Engineering Skills→
sasamukusasamuku
8

squash-commits

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

Community
Intermediate
antonyfmunozantonyfmunoz

git

Manage Git version control tasks for EOS code with commit, branch, merge, and push workflows.

Community
Intermediate
vrcmsvrcms
1

git-workflow

Standardize Git branching, commit conventions, and merge workflows.

Community
Intermediate
maggitmaggit

rebase

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

Community
Intermediate