Skip to content
Back to skills

Waffle Render

ASecurity

Re-render this repo's current wafflestack selection into harness-native files (.claude/ etc.) and refresh the lock. Use after editing `.waffle/waffle.yaml` or upgrading the toolkit.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 19, 2026
ai-agentsbashgit

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add dustinkeeton/wafflestack --skill waffle-render --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Waffle Render?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Waffle Render
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dustinkeeton-waffle-render-wafflestack/badge)](https://www.skillsdirectory.com/skills/dustinkeeton-waffle-render-wafflestack)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: waffle-render
description: Re-render this repo's current wafflestack selection into harness-native files (.claude/ etc.) and refresh the lock. Use after editing `.waffle/waffle.yaml` or upgrading the toolkit.
user-invocable: true
argument-hint: "(no refs — use /waffle-install to add one; --force overwrites unmanaged collisions; --gitignore adds recommended entries)"
---

# Re-render the current selection

Wraps `wafflestack render` — it regenerates every managed file verbatim from the current
`.waffle/waffle.yaml` selection, refreshes `.waffle/waffle.lock.json`, and **prunes**
previously-managed files that are no longer produced. It takes **no refs** (use
**`/waffle-install`** to add a stack or item — that persists the choice, then renders); bare
`render` re-renders what is already selected.

## Run it

```bash
npx --yes {{waffle.toolkitRef}} render
```

`bake` is a pure alias — `wafflestack bake` is `wafflestack render`, same flags, same behavior.

Pass `--force` or `--gitignore` through only if `$ARGUMENTS` asks (see the collision note below
for when `--force` is appropriate).

## Interpret the result

- **Report the counts.** Relay `rendered N files into <dir>` and any `removed stale: …` line
  (files pruned because the selection dropped them or an item was ejected).
- **Missing required config.** A `config.<stack>.<key>` error means a required key is unset —
  add it to `.waffle/waffle.yaml` `config:` (or `.waffle/waffle.local.yaml` for
  account-specific values) and re-render.
- **Unmanaged-file collision.** The render refuses to overwrite a file it did not write (a
  hand-authored file at a path a render targets), naming every offender and writing **nothing**.
  Do not reach for `--force` reflexively — it discards their content. Explain the collision and
  offer to move the file aside or fold it into a `.waffle/extensions/` file first; `--force`
  only once the user decides the toolkit should own that path.
- **Never hand-edit the output.** The rendered `.claude/` tree is generated — a local edit is
  drift (**`/waffle-doctor`** flags it, and this render restores it). Add project-specific
  guidance through `.waffle/extensions/` instead.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…