skills.rest
Abildtoft
AbildtoftCOMMUNITY
Explore all skills by this author →
GitHub

kramme:recreate-commits

Rewrite a branch's commit history into narrative-quality single-idea commits.

2|2|Updated Jan 15, 2026
Search Tags:#git#rebase#code-review#branch-management#commit-history#narrative-commits
One-click install
npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-recreate-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kramme:recreate-commits
Source: https://github.com/Abildtoft/kramme-cc-workflow/tree/main/skills/kramme%3Arecreate-commits
Command: npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-recreate-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you transform a messy or incomplete commit history on your current branch into a clear, narrative sequence that is easy for reviewers to understand.

Core Features & Use Cases

  • Story-driven commits: Break down changes into small, coherent commits with descriptive messages.
  • Safe rewrite workflow: Replays commits onto the merge-base, preserving the final state while improving clarity.
  • Use Case: Before opening a pull request, apply this skill to produce a reviewer-friendly history with focused, single-idea commits.

Quick Start

Follow prompts to plan and re-create the commit history for your current branch.

Frequently Asked Questions about kramme:recreate-commits

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

FAQPage Schema
How do I rewrite git commit history for a cleaner pull request?▼

To rewrite git commit history for a cleaner pull request, this Skill replays your changes onto the merge-base. It resets your current feature branch and recreates commits as single-idea, descriptive narrative sequences for reviewers.

What is a narrative commit history and when do I need it?▼

A narrative commit history is a sequence of small, coherent commits that tell a clear story of changes. You need it during code reviews, PR preparation, or release management to make your branch easier for reviewers to understand.

How do I rebase messy commits into single-idea commits before code review?▼

To rebase messy commits into single-idea commits, this Skill identifies your base branch, plans the commit story, resets to the base, and recreates commits. This safe rewrite workflow preserves your final state while improving clarity.

Does recreating commits on a feature branch preserve my current code changes?▼

Recreating commits on a feature branch preserves your current code changes completely. The workflow replays your final state onto the merge-base, ensuring no work is lost while producing a reviewer-friendly commit history.

What is the best way to prepare a feature branch for release?▼

The best way to prepare a feature branch for release is to transform its commit history into a clear narrative. This Skill breaks down changes into focused, descriptive commits suitable for active development and release preparation.

Related Skills

Explore More Software Engineering Skills→
kage1020kage1020

diff-report

Analyze branch changes and generate a five-section Markdown diff report.

Community
Intermediate
ivanov-iivanov-i

git-clean-history

Rewrite a feature branch onto a clean branch off main with narrative commits.

Community
Advanced
bennybennisonbennybennison

git-commit-discipline

Enforce consistent git commit messages and clean branch history.

Community
Intermediate
ilamanovilamanov

reimplement-branch

Reimplement a git branch with a narrative-quality commit history.

Community
Intermediate