docs: fix confusing --kiro-dir example to avoid nested specs/specs/ structure #100
Conversation
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
…tructure Changed --kiro-dir example from docs/specs to docs across all README files to prevent confusing docs/specs/specs/ directory structure. Fixes gotalab#99 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Owner
|
Everything looks good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Fixed the
--kiro-direxample in all README files to usedocsinstead ofdocs/specsto prevent confusing nested directory structure.Changes
--kiro-dir docs/specs→--kiro-dir docs--kiro-dir docs/specs→--kiro-dir docs--kiro-dir docs/specs→--kiro-dir docs--kiro-dir docs/specs→--kiro-dir docsProblem
When users followed the README example using
--kiro-dir docs/specs, specification files were placed indocs/specs/specs/, creating a confusing nested structure.Solution
By using
--kiro-dir docsinstead, specification files will be placed indocs/specs/, which is clearer and more intuitive.Fixes #99
🤖 Generated with Claude Code