Reimplement the current branch on a new branch with a clean, narrative-quality git commit history.
SkillScore83Maintained
Automatic
◆Coding pack
Last verified 8/9/2026
What it changes
Passed 17 of 20 test cases with the skill, and 16 of 20 without it.
Without skill78%
With skill83%
Checks it passed that the model alone missed
Specifies running `git log main..HEAD --oneline`
Excludes AI attribution from pull request body text
Excludes the `--no-verify` flag from the final commit
3 fixed16 passed either way2 still failing2 broke
Pass-rate lift
+4 pp
Tokens
-33%
Agent turns
0%
Response time
-61%
Model gemini-3.6-flashMeasured 8/9/2026v119 of 23 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
When retrieving existing commit subjects on the current topic branch relative to main before rebuilding commit history, which exact git log command line should be executed?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies running `git log main..HEAD --oneline`
Missed
Passed
case-07 · gemini-3.6-flash · 8/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md41 linessingle file
Clean copy
Reimplement the current branch on a new branch with a clean, narrative-quality commit history suitable for reviewer comprehension.
Workflow
Gather context:
Source branch: git branch --show-current.
Working tree: git status --short.
Commits since main: git log main..HEAD --oneline.
Diff summary: git diff main...HEAD --stat.
Validate the source branch:
Ensure there are no uncommitted changes or merge conflicts.
Confirm the source branch is up to date with main.
Choose the new branch name:
Use the user's requested name when provided.
Otherwise use <source-branch>-clean.
Analyze the diff:
Study all changes between the source branch and main.
Understand the final intended state before recreating it.
Create the clean branch from main.
Plan the commit storyline:
Break the implementation into self-contained logical steps.
Each step should read like a stage of development in a tutorial.
Reimplement the work:
Recreate the final changes step by step.
Commit after each coherent idea.
Use clear commit subjects and descriptions.
Use git commit --no-verify for intermediate commits so hooks do not block temporarily incomplete states.
Verify correctness:
Confirm the final clean branch state exactly matches the original source branch.
Run the final commit without --no-verify so normal checks run.
Open a pull request using the pr skill.
Include a link to the original branch in the PR description.
Rules
Never add yourself or an AI tool as an author, contributor, or co-author.
Never include AI attribution in commits or PR content.
The final clean branch must be identical to the source branch.