preferences-git-history-cleanup

Automate non-interactive Git history cleanup with reordering, squashing, fixup, dropping, and rewording.

14|Updated May 28, 2024
One-click install
npx skills add https://github.com/cameronraysmith/vanixiets --skill preferences-git-history-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preferences-git-history-cleanup
Source: https://github.com/cameronraysmith/vanixiets/tree/main/modules/home/ai/skills/src/core/preferences-git-history-cleanup
Command: npx skills add https://github.com/cameronraysmith/vanixiets --skill preferences-git-history-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of cleaning up Git commit history, ensuring a clear, atomic, and reviewable narrative of changes before merging.

Core Features & Use Cases

  • Non-Interactive History Rewriting: Reorder, squash, fixup, drop, and reword commits without manual editor intervention using GIT_SEQUENCE_EDITOR.
  • Robust Scripting: Provides patterns for complex edits using temporary files and multi-step workflows.
  • Use Case: Before submitting a pull request, use this Skill to squash several small, incremental commits into a single, meaningful commit that represents the complete feature.

Quick Start

Use the preferences-git-history-cleanup skill to squash the last 3 commits into one.

Frequently Asked Questions about preferences-git-history-cleanup

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

FAQPage Schema
How do I squash git commits non-interactively without opening an editor?

Squash git commits non-interactively by using `GIT_SEQUENCE_EDITOR` to automate rebase sequences, allowing you to reorder, fixup, drop, and reword commits without manual editor intervention.

What is the best way to automate git history cleanup for a pull request?

Automate git history cleanup for pull requests by squashing incremental commits into a single meaningful commit, ensuring a clear, atomic, and reviewable narrative of changes before merging.

Can I script complex git rebase operations to reorder and drop commits?

Yes, you can script complex git rebase operations to reorder and drop commits using temporary files and multi-step workflows, providing deterministic and scriptable git history manipulation.

Does non-interactive git history rewriting work for revising old commit messages?

Non-interactive git history rewriting works for revising old commit messages by applying scripted reword operations through automated sequence editors, bypassing the need for manual text editing.

When should I use non-interactive rebase instead of manual git history editing?

Use non-interactive rebase instead of manual git history editing when you need precise control over commit sequences in a deterministic, scriptable workflow, avoiding manual editor interaction.