Skip to content

feat(init)!: render the template into the checkout's spectre directory - #56

Merged
jvmakine merged 1 commit into
mainfrom
juho/init-into-spectre
Oct 22, 2026
Merged

jvmakine merged 1 commit into
mainfrom
juho/init-into-spectre

Conversation

@jvmakine

Copy link
Copy Markdown
Collaborator

A template wrote files across the checkout: the Dockerfile and build script at the root, the agent skills under .agents/ and .claude/, and the rest under spectre/. Updating a service from a newer template then meant knowing which files outside spectre/ it owned.

spectre init now renders the template's root into <dir>/spectre/, so everything a template writes is in that one directory. The checkout must exist, and init still refuses one whose spectre/ already exists.

🤖 Generated with Claude Code

Templates wrote files across the checkout, so updating one meant tracking
which files outside spectre/ it owned. Rendering the whole template into
spectre/ keeps everything it writes in one directory the template owns.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@jvmakine
jvmakine requested a review from alecthomas as a code owner October 22, 2026 23:43
@jvmakine
jvmakine merged commit 451545e into main Oct 22, 2026
6 checks passed
@jvmakine
jvmakine deleted the juho/init-into-spectre branch October 22, 2026 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant