Skip to content

refactor(init): stop prescribing a .scratch directory - #31

Merged
kixelated merged 1 commit into
mainfrom
claude/remove-scratch-prescriptions-b956c7
Sep 30, 2026
Merged

kixelated merged 1 commit into
mainfrom
claude/remove-scratch-prescriptions-b956c7

Conversation

@kixelated

Copy link
Copy Markdown
Owner

Problem

quest init appended /.scratch/ to .gitignore, and the start skill told agents to keep PR bodies, logs, and notes there. Where to put scratch files is a choice for each repository, so Quest shouldn't decide it.

Resulting behavior

  • quest init and quest uninstall no longer touch .gitignore. They only manage the skill stubs, quest/README.md, and the reference line.
  • The start skill no longer names a scratch location. It still says never to write to or clean up a directory that other agents share.
  • Removed this repo's own /.scratch/ ignore entry, which only existed because of the skill.
  • append_line lost its paragraph flag, since only the reference line uses it now.

No release has been tagged, so uninstall doesn't keep cleaning up /.scratch/ lines left by earlier inits.

Validation

  • nix develop -c just check passes.
  • nix develop -c just test passes (77 tests). init_creates_layout_and_is_idempotent now asserts that no .gitignore is created.

(written by Claude Opus 5.5)

🤖 Generated with Claude Code

`quest init` added `/.scratch/` to `.gitignore` and the start skill told
agents to keep scratch files there. That convention belongs to individual
repositories, not to Quest. Init and uninstall no longer touch
`.gitignore`, and the start skill no longer names a scratch location.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kixelated
kixelated marked this pull request as ready for review September 30, 2026 19:50
@kixelated
kixelated merged commit 362489b into main Sep 30, 2026
7 checks passed
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