amend-non-last-commit

Reword non-head commit messages without launching an editor.

Updated Aug 23, 2026

Search Tags:#git #commit #amend #version-control #non-interactive #reword

Ready to run

npx skills add https://github.com/jarodmeng/daydreamedu-scripts --skill amend-non-last-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: amend-non-last-commit
Source: https://github.com/jarodmeng/daydreamedu-scripts/tree/main/.cursor/skills/amend-non-last-commit
Command: npx skills add https://github.com/jarodmeng/daydreamedu-scripts --skill amend-non-last-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rewords the commit message of a non-head commit without launching an editor, enabling clean history edits.

Core Features & Use Cases

Non-interactive commit message amendments for older commits, e.g. adding "Fixes #6" or rewording the subject.
Rebase-free workflows that avoid manual editor prompts during history rewrites.
Works with environment variables to drive the new message in automation pipelines.

Quick Start

Identify the target non-head commit and run the non-interactive amend workflow to set the new message.

Frequently Asked Questions about amend-non-last-commit

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

FAQPage Schema

How do I reword an older git commit message without opening an editor?▼

Reword an older git commit message without opening an editor by using a non-interactive amend workflow that sets the new message through environment variables. It uses a single amend -m invocation to avoid manual editor prompts during history rewrites.

Can I add a GitHub issue link to a past commit in a non-interactive pipeline?▼

Yes, you can add a GitHub issue link to a past commit in a non-interactive pipeline by using environment variables to drive the new message. This supports script-driven workflows like adding "Fixes #6" without launching an editor.

What is the best way to amend a non-head commit in an automated script?▼

Amending a non-head commit in an automated script is best done through a rebase-free workflow that uses environment variables and a single amend -m invocation. This approach preserves script-driven workflows by avoiding interactive rebases entirely.

Does this non-interactive amend method require an interactive rebase to update past messages?▼

No, this non-interactive amend method does not require an interactive rebase to update past messages. It avoids interactive rebases and manual editor prompts entirely by using environment variables to set the new commit message.

How do I change a git commit subject without launching an editor during history rewrites?▼

Change a git commit subject without launching an editor during history rewrites by using a non-interactive amend workflow. It sets the new message through environment variables and a single amend -m invocation to enable clean history edits.

Are there limitations when using environment variables to amend non-last commits?▼

The amend-non-last-commit workflow is limited to rewording commit messages and cannot alter commit content. It is specifically designed for non-interactive pipelines and script-driven workflows that use environment variables to set the new message.