Rename Git Commits for Openclaw

A specialized technical workflow designed to rewrite commit messages in git history safely and efficiently without relying on interactive pseudo-terminals (PTYs).

tomekdot
v1.1.0
Jun 13, 2026
0
131
4

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install rename-git-commits

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install rename-git-commits using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Rename Git Commits?

The Rename Git Commits workflow provides a highly robust blueprint for modifying commit messages across different states of your version control lifecycle. It solves a notorious problem in automated environments and Windows/MSYS setups where interactive git rebasing fails due to the lack of a proper PTY (Pseudo-Terminal). By establishing clear, programmatic alternatives to interactive rebasing, it allows developers and automated agents to correct typos, standardize capitalization, or append critical missing context to past commits.

Leveraging this tool within Openclaw Skills ensures your repository maintenance remains seamless and scriptable. It outlines definitive paths for modifying the most recent commit, rewriting multiple chronological commits, or handling commits that have already been pushed to a remote server while strictly enforcing safety boundaries to prevent collaborative history disruption.

Rename Git Commits Use Cases

  • Fixing typographical errors, formatting mistakes, or incorrect casing in recent commit messages.
  • Standardizing git history to match specific project rules, such as replacing lowercase starting letters with capital letters.
  • Injecting omitted context, issue numbers, or metadata into previous commits before pushing upstream.
  • Creating non-interactive, safe git maintenance scripts within automated pipelines or Windows/MSYS developer environments.

How Rename Git Commits Works

  1. Context Evaluation: The workflow evaluates whether the target commits exist solely on the local machine or if they have already been pushed to a shared remote repository.
  2. Strategy Selection: Based on the location and depth of the targeted commits, it selects either a direct amend (for the latest commit), a structural reset and cherry-pick loop (for multiple older commits), or a follow-up empty commit (for pushed, shared history).
  3. History Manipulation: The selected method executes without launching interactive text editors by injecting message arguments natively or using non-interactive stream editors like sed.
  4. Verification & Synchronization: The developer or agent inspects the newly constructed history graph using oneline logs, and synchronizes upstream using a lease-protected push operation if working with unshared remote branches.

Rename Git Commits Setup

To integrate and utilize this workflow within Openclaw Skills, ensure git is configured properly in your terminal environment. No heavy third-party installation is needed, as it relies on standard git binaries.

Verify your git version and ensure compatibility with modern push flags:

git --version

For Windows or MSYS environments where interactive terminals are constrained, save the structural cherry-pick or non-interactive sequence command logic directly into your automation script workflows.

Rename Git Commits Data Schema & Taxonomy

This skill acts directly on your local git repository's internal object database (.git/). It organizes execution and tracking across the following operational schema:

Data Component Type Description
backup-main Git Branch A temporary reference branch created to preserve original state before history modification.
COMMIT_HASH SHA-1 / SHA-256 The unique cryptographic identifier pointing to the commit preceding your targets.
GIT_SEQUENCE_EDITOR Environment Variable Injected command string using sed to bypass interactive text menus during standard rebase operations.
git log --oneline Output Metadata The primary validation format used to verify modified message strings post-execution.

Rename Git Commits Advanced Features

  • PTY-Free Multi-Commit Rewriting: Modifies multiple historical blocks concurrently on automation runners and Windows environments by leveraging the --no-commit flag during strategic cherry-picks.
  • Lease-Protected Pushing: Promotes historical changes to remote servers using origin --force-with-lease rather than a standard force push, guaranteeing no upstream work by other developers is overwritten.
  • Non-Interactive Sequence Injection: Employs programmatically overridden sequence editors (GIT_SEQUENCE_EDITOR="sed -i...") to replace interactive 'pick' instructions with 'reword' commands seamlessly.
  • Safe Fallback Generation: Programmatically switches to empty tracking commits when upstream branch protections or collaboration rules prohibit history rewriting.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*