rebake 0.0.1

A spiritual successor to cruft for managing cookiecutter projects

rebake

A spiritual successor to cruft for managing cookiecutter projects.

rebake improves on cruft in two key areas:

1. Better conflict UX — uses git apply -3 to produce inline conflict markers instead of .rej files
2. New variable detection — prompts for variables added to the template since the project was last updated

Requirements

• Python 3.12+
• uv
• Git

Installation

uv tool install rebake

Or add it to a project:

uv add rebake

Usage

rebake check

Check whether the project is up-to-date with its template.

rebake check [PROJECT_DIR]

Exit codes:

• 0 — up-to-date
• 1 — outdated
• 2 — error (e.g. .cruft.json not found)

rebake update

Apply the latest template changes to the project.

rebake update [PROJECT_DIR]

rebake will:

1. Abort if there are uncommitted changes (commit or stash first)
2. Detect new variables added to the template and prompt for their values
3. Generate a diff between the old and new rendered templates
4. Apply the diff with git apply -3 — conflicts appear as inline markers
5. Update .cruft.json with the new commit hash and any newly added variables

Migrating from cruft

rebake reads .cruft.json as-is. No migration needed — just replace cruft with rebake in your commands.

# before
cruft check
cruft update

# after
rebake check
rebake update

.cruft.json format

{
  "template": "https://github.com/owner/template",
  "commit": "abc123...",
  "checkout": "main",
  "context": {
    "cookiecutter": {
      "project_name": "my-project",
      "author": "Jane Doe"
    }
  },
  "skip": ["go.sum", "*.lock"]
}

Development

git clone https://github.com/kitagry/rebake
cd rebake
uv sync
uv run pytest