Skip to content

feat: apply default template automatically when creating new directories#9

Merged
stephendolan merged 1 commit into
mainfrom
feat/default-template
Dec 5, 2025
Merged

feat: apply default template automatically when creating new directories#9
stephendolan merged 1 commit into
mainfrom
feat/default-template

Conversation

@stephendolan

Copy link
Copy Markdown
Owner

Summary

Removes hardcoded README generation in favor of automatic "default" template application. When creating new directories without --template, scry now checks for ~/.config/scry/templates/default/ and applies it if present, otherwise creates an empty directory.

Problem

Users had no control over the default content created in new scry directories - the hardcoded README with vendor-specific "exploratory project" messaging didn't match everyone's workflow.

Core Changes

  • Removed generate_readme() function that created hardcoded vendor-specific content
  • Added automatic "default" template lookup when no --template flag specified
  • Updated help text to document the new behavior
  • Bumped version to 0.5.0

🤖 Generated with Claude Code

Previously, new scry directories were created with hardcoded README
content generated from the directory name. This forced vendor-specific
content on all users.

Now checks for ~/.config/scry/templates/default/ and applies it
automatically when no --template flag is specified. If no default
template exists, creates an empty directory. This gives users control
over their default experience through templates instead of hardcoded
content.

Changes:
- Remove generate_readme() function with hardcoded content
- Auto-apply "default" template if it exists
- Update help text to document new behavior
- Bump version to 0.5.0

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@stephendolan stephendolan merged commit a8568b9 into main Dec 5, 2025
4 checks passed
@stephendolan stephendolan deleted the feat/default-template branch December 5, 2025 18:00
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