Fix template path inconsistency between init and init --here #437
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.
Problem
When using specify
init --here
, thecreate-new-feature.sh
script was looking for templates in$REPO_ROOT/templates/
but they were actually placed in$REPO_ROOT/.specify/templates/
. This caused:spec-template.md
Solution
Updated
scripts/bash/create-new-feature.sh
to use the correct path by changingTEMPLATE="$REPO_ROOT/templates/spec-template.md"
toTEMPLATE="$REPO_ROOT/.specify/templates/spec-template.md"
Impact
Both
specify init
andspecify init --here
now consistently use.specify/templates/
Mitigate Unicode corruption in generated spec files in Claude Code. The Unicode corrupted while writing is still need to be fixed in Claude Code
Aligns with update-agent-context.sh which already uses the correct path
Fixes Special characters and emojis from spec-template.md not being carried to spec.md #248