feat: apply default template automatically when creating new directories#9
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
generate_readme()function that created hardcoded vendor-specific content--templateflag specified🤖 Generated with Claude Code