rebake 0.1.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. Partial apply on conflict — uses git apply --reject to apply all applicable hunks; only the unresolvable portions are saved as .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

Quick Start

uvx rebake check
uvx rebake update

No installation required. Uses uv.

Installation

To install permanently:

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] [OPTIONS]

rebake will:

1. Abort if there are uncommitted changes (commit or stash first)
2. Run pre-update hooks (if defined) — abort if any hook fails
3. Detect new variables added to the template and prompt for their values
4. Generate a diff between the old and new rendered templates
5. Apply the diff with git apply --reject — applicable hunks are written immediately; unresolvable hunks are saved as .rej files for manual resolution
6. Update rebake.yaml with the new commit hash and any newly added variables
7. Run post-update hooks (if defined)

Options

Option	Description
--allow-untracked-files	Allow update even if untracked files exist (no other changes)
--quiet	Disable interactive prompts; exit 1 if new variables are found without a supplied value
--checkout, -c	Branch, tag or commit to follow

Hooks

Define shell commands to run before or after the update in rebake.yaml:

hooks:
  pre-update:
    - make lint          # runs before the patch is applied; abort on failure
  post-update:
    - go generate ./...  # runs after rebake.yaml is saved; abort on failure
    - make fmt

Hooks run in the project directory with the following environment variables available:

Variable	Value
REBAKE_TEMPLATE	Template repository URL
REBAKE_OLD_COMMIT	Commit hash before the update
REBAKE_NEW_COMMIT	Commit hash after the update
REBAKE_PROJECT_DIR	Absolute path to the project directory

Non-interactive usage (e.g. from an LLM agent)

--quiet is designed for automated workflows where interactive prompts are not possible.

# Attempt update non-interactively; exit 1 if new variables need values
rebake update --quiet

When --quiet is used and new variables are found, rebake prints each variable name and its default value to stderr, then exits with code 1.

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

rebake.yaml format

template: https://github.com/owner/template
commit: abc123...
checkout: main          # optional: branch/tag/commit to track
context:
  cookiecutter:
    project_name: my-project
    author: Jane Doe
skip:                   # optional: file patterns to skip
  - go.sum
  - "*.lock"
hooks:                  # optional: shell commands to run on update
  pre-update:
    - make lint
  post-update:
    - make fmt

Development

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