-
Notifications
You must be signed in to change notification settings - Fork 7.2k
Clarify CLI reference usage in README #2001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ArthurFay
wants to merge
1
commit into
github:main
Choose a base branch
from
ArthurFay:fix-cli-docs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+2
−2
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -287,7 +287,7 @@ Community projects that extend, visualize, or build on Spec Kit: | |
| ## 🔧 Specify CLI Reference | ||
|
|
||
| The `specify` command supports the following options: | ||
|
|
||
| The examples below assume you used the persistent installation method from the Get Started section, so the `specify` command is available directly in your PATH. If you are using the one-time usage method instead, run the equivalent commands with `uvx --from git+https://github.com/github/[email protected] specify ...`. | ||
| ### Commands | ||
|
|
||
| | Command | Description | | ||
|
|
@@ -314,7 +314,7 @@ The `specify` command supports the following options: | |
| | `--branch-numbering` | Option | Branch numbering strategy: `sequential` (default — `001`, `002`, `003`) or `timestamp` (`YYYYMMDD-HHMMSS`). Timestamp mode is useful for distributed teams to avoid numbering conflicts | | ||
|
|
||
| ### Examples | ||
|
|
||
| Examples below use the persistent installation form. If you did not install the CLI persistently, use the `uvx --from git+https://github.com/github/[email protected] specify ...` form instead. | ||
| ```bash | ||
| # Basic project initialization | ||
| specify init my-project | ||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Markdown collapses single newlines into one paragraph, so this renders as: “The
specifycommand supports the following options: The examples below assume…”, which reads like a run-on sentence due to the colon. Consider inserting a blank line and/or changing the colon to a period so the installation assumption is a separate paragraph.