re0-upgrade
Bring your installed paperthin skills up to the full current catalog in one step: retire…
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.
$ npx -y skills add LilMGenius/paperthin --skill re0-git --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/re0-gitContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
name: re0-git disable-model-invocation: true 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."
Rewrite a finished commit message so the log hands off on its own — in the author's own voice, not an imposed one.
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.
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.
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.
Turning old engineering wisdom into reflexes your agent reaches for on its own. On any agent | Claude Code, Codex, OpenCode, Antigravity, Copilot, Cursor, Grok-Build, Pi, Hermes, OpenClaw, etc.
Repo: LilMGenius/paperthin
Bring your installed paperthin skills up to the full current catalog in one step: retire…
Audit and consolidate a fact that's scattered across places into one canonical source, after…
Rebuild the human's lost context on a project from live state, in plain language: what needs…
Read the live cycle state and return the single highest-leverage next best action, not a…
Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting…
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns,…