Agent skill

Re0 Git

by LilMGenius in LilMGenius/paperthin

Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story.

MITAuto-check passedDevelopment

Install Re0 Git

skills CLI
$ npx skills add LilMGenius/paperthin --skill re0-git -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LilMGenius/paperthin re0-git --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LilMGenius/paperthin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/depth/re0-git .claude/skills/re0-git && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
re0-git
GitHub stars
1.1k
Token cost
~1k tokens
SKILL.md length
622 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story.

  • Works in 6 steps: Scope the target — usually HEAD,… → Read the change (git show --stat, git… → Resolve mixed logs in this order:… → …
  • Tasks that involve Git workflow
  • SKILL.md covers Goal, Workflow, Rules and Verification
  • Calls git

What it does

Re0 Git is an agent skill from LilMGenius/paperthin. Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow. It works with Git. The repository describes itself as: Low-level agentic design patterns. Turning old engineering wisdom into reflexes your agent reaches for on its own—on any agent. The licence is MIT.

When your agent uses it

  • Tasks that involve Git workflow

Example prompts

  • “/re0-git”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Scope the target — usually HEAD, sometimes a short unpushed range.
  2. Read the change (git show --stat, git diff) and any documented commit rules. Then sample nearby non-target messages: start with 10, stop…
  3. Resolve mixed logs in this order: documented project rules, nearby commits touching the same area, then same-author commits within that…
  4. Rewrite the message to the commit-economy (below): keep only durable handoff facts, fold supporting edits into the change they serve, and…
  5. Re-commit signed, dates per the rule below. For the tip (HEAD): git commit --amend -S --date=now — the --date=now is what moves the author…
  6. Verify and report.

What it can do on your machine

Read from SKILL.md and the folder at commit 7d5dc62. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Re0 Git loads about 1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 622 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LilMGenius/paperthin at commit 7d5dc62, republished under its MIT licence (© LilMGenius). 622 words, ~1,029 tokens.

Download SKILL.mdSave it as .claude/skills/re0-git/SKILL.md (or your agent's skills folder).
name
re0-git
description
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so `git log` alone tells the story. User-invoked: run it after a commit.
disable-model-invocation
true

Rewrite a finished commit message so the log hands off on its own — in the author's own voice, not an imposed one.

Goal

Repeated amends and momentum commits leave a message bloated, stale, or padded with trivia. re0-git rewrites the message into a clean version that lets a fresh session continue from git log alone, without reading the diff. It refines what the author already writes. Only the message moves — and timestamps, per the date rule below; the tree never changes.

It is user-invoked — run it once you've decided to commit. A commit-cleanup tool in the agent's reach would bias it toward committing when it shouldn't.

Workflow

  1. Scope the target — usually HEAD, sometimes a short unpushed range.
  2. Read the change (git show --stat, git diff) and any documented commit rules. Then sample nearby non-target messages: start with 10, stop earlier if the convention is obvious, or expand only until the convention is clear.
  3. Resolve mixed logs in this order: documented project rules, nearby commits touching the same area, then same-author commits within that convention. Do not average incompatible styles or let one author's habits override the repo.
  4. Rewrite the message to the commit-economy (below): keep only durable handoff facts, fold supporting edits into the change they serve, and cut anything the diff or tag already proves. Give trivia no bullet of its own.
  5. Re-commit signed, dates per the rule below. For the tip (HEAD): git commit --amend -S --date=now — the --date=now is what moves the author date to now; a bare --amend resets only the committer date and leaves the author date stale. For an older commit, keeping its dates: rebuild it — GIT_AUTHOR_DATE/GIT_COMMITTER_DATE git commit-tree <tree> -p <parent> -S -m "<new message>" — then replay every descendant onto the rebuilt commit (a non-tip rewrite is a rebase, not a ref move), or you orphan them.
  6. Verify and report.
Show full SKILL.md (309 more words)Show less

Rules

  • Never create or suggest a commit — re0-git only rewrites the message of a commit that already exists. Using it is never a reason to commit.
  • Message only — the tree must stay byte-identical (git diff <old> <new> empty); never edit content in a re0-git pass.
  • commit-economy — the commit-message standard this skill enforces: one bullet per real, durable change with supporting edits folded in, nothing the diff or version already proves, no co-author tags, matched to the local log's own shape (sampled above). Where that sampling finds no settled shape, fall back to a subject line, a blank line, then one - bullet per change on a single unwrapped line — never prose paragraphs, which explain where a log should list. A step a documented checklist already mandates for any change of this shape (registering a new skill, syncing translated docs after a source edit) is proof the process ran, not a fact about this change — fold it as a trailing clause on the bullet it serves, or drop it if that bullet already implies it; it earns a bullet of its own only when something about how it was done is itself non-obvious. The same bar governs the first draft; re0-git only enforces it on a message that already drifted past it.
  • Dates by position; always gpg-signed. The commit you're finalizing — HEAD — takes both author and committer date = now, because re-cleaning the latest commit is itself continued work. Every older commit (HEAD~1 and back) keeps its original author + committer dates; never restamp the past.
  • Never rewrite pushed or shared history without explicit confirmation — it forces a force-push.

Verification

  1. git diff <old-tip> <new-tip> is empty — content unchanged.
  2. Each rewritten commit is gpg-signed (%G? = G) with dates as intended.
  3. Re-read git log alone, diff hidden — if any cut line turns out to be needed to follow the change, restore it.

© LilMGenius, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/depth/re0-git of LilMGenius/paperthin.

Open the folder on GitHubat commit 7d5dc62

Compare with similar skills

Re0 Git next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Re0 Git compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Re0 Git this skillLilMGenius/paperthin1.1k—~1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost55k—~3.8kAutomated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Git Merge Conflict Resolver

    tailcallhq/forgecode

    Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.

    7.6k GitHub starsUsed in 1 repo~4.5k tokens
    DevelopmentAuto-check passed

More from LilMGenius/paperthin

All 28 skills in this repo
  • Modelchk

    LilMGenius/paperthin

    Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the…

    1.1k GitHub stars~1.6k tokensUpdated 7 days ago
    Auto-check passed
  • Re0 Loop

    LilMGenius/paperthin

    Run repeated build - QA - re0-memo - re0-work cycles while preserving learning and letting code die.

    1.1k GitHub stars~579 tokensUpdated 7 days ago
    Auto-check passed
  • Autobahn

    LilMGenius/paperthin

    Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved…

    1.1k GitHub stars~2.1k tokensUpdated 7 days ago
    Auto-check passed
  • Catchup

    LilMGenius/paperthin

    Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean.

    1.1k GitHub stars~785 tokensUpdated 7 days ago
    Auto-check passed
  • Debloat

    LilMGenius/paperthin

    Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved.

    1.1k GitHub stars~813 tokensUpdated 7 days ago
    Auto-check passed
  • Factchk

    LilMGenius/paperthin

    Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established?

    1.1k GitHub stars~717 tokensUpdated 7 days ago
    Auto-check passed

Works with

Categories

Questions about Re0 Git

What does Re0 Git do?

Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. Re0 Git is an agent skill from LilMGenius/paperthin. Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story.

When should I use Re0 Git?

Re0 Git fits situations like: tasks that involve Git workflow.

How do I install Re0 Git in Claude Code?

Run `npx skills add LilMGenius/paperthin --skill re0-git -a claude-code`. Or copy the skill folder (skills/depth/re0-git in LilMGenius/paperthin) into .claude/skills/re0-git in your project. Claude Code loads it when a task matches its description.

How do I install Re0 Git in Codex?

Run `npx skills add LilMGenius/paperthin --skill re0-git -a codex`. Or copy the skill folder (skills/depth/re0-git in LilMGenius/paperthin) into .agents/skills/re0-git in your project. Codex loads it when a task matches its description.

Can I use Re0 Git in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LilMGenius/paperthin --skill re0-git -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/re0-git, .gemini/skills/re0-git, .github/skills/re0-git and .opencode/skills/re0-git in your project.

What does Re0 Git need to run?

Going by SKILL.md and its folder, Re0 Git needs the command-line tools its instructions call (git).

Does Re0 Git access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Re0 Git safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Re0 Git use?

Re0 Git is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Re0 Git use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Re0 Git?

Skills that share tags, products or a category with Re0 Git: Finishing a Development Branch (obra/superpowers, 296k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Re0 Git?

LilMGenius (a GitHub user) maintains it in LilMGenius/paperthin, which has 1,130 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 1, 2026.

Source: LilMGenius/paperthin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.