Skip to content

Commit b6bccdd

Browse files
fsilvaortizclaude
andcommitted
fix: clarify --json flag requirement per Copilot review
- Rephrased step 2 to mention both --short-name and --json flags - Added explicit note to always include the JSON flag for reliable output parsing Co-Authored-By: Claude Opus 4.6 <[email protected]>
1 parent f092033 commit b6bccdd

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

‎templates/commands/specify.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,13 +39,14 @@ Given that feature description, do this:
3939
- "Create a dashboard for analytics" → "analytics-dashboard"
4040
- "Fix payment processing timeout bug" → "fix-payment-timeout"
4141

42-
2. **Create the feature branch** by running the script with only `--short-name` (do NOT pass `--number` — the script auto-detects the next globally available number across all branches and spec directories):
42+
2. **Create the feature branch** by running the script with `--short-name` (and `--json`), and do NOT pass `--number` (the script auto-detects the next globally available number across all branches and spec directories):
4343

4444
- Bash example: `{SCRIPT} --json --short-name "user-auth" "Add user authentication"`
4545
- PowerShell example: `{SCRIPT} -Json -ShortName "user-auth" "Add user authentication"`
4646

4747
**IMPORTANT**:
4848
- Do NOT pass `--number` — the script determines the correct next number automatically
49+
- Always include the JSON flag (`--json` for Bash, `-Json` for PowerShell) so the output can be parsed reliably
4950
- You must only ever run this script once per feature
5051
- The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for
5152
- The JSON output will contain BRANCH_NAME and SPEC_FILE paths

0 commit comments

Comments
 (0)