fix(extensions): hyphenate command names in the Forge post-install listing#3669
Merged
mnriem merged 1 commit intoJul 23, 2026
Merged
Conversation
…sting After `specify extension add`, the "Provided commands" summary hyphenated command names only for Cline. For a Forge project the names were printed in dotted form (e.g. `speckit.test-ext.hello`), but Forge registers them hyphenated (`speckit-test-ext-hello`), so the printed names didn't match what the user actually invokes in Forge. Extend the existing Cline handling to Forge via `format_forge_command_name`, completing the Forge command-name parity already fixed for hook invocations (github#3641) and the init next-steps panel (github#3642). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes Forge’s extension post-install summary to display the command names users can actually invoke.
Changes:
- Detects Forge projects and formats listed commands with hyphens.
- Adds regression coverage for Forge extension installation output.
Show a summary per file
| File | Description |
|---|---|
src/specify_cli/extensions/_commands.py |
Applies Forge command-name formatting to the provided-commands listing. |
tests/test_extensions.py |
Verifies Forge listings use hyphenated names. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Medium
Collaborator
|
Thank you! |
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.
What
After
specify extension add, the "Provided commands" summary hyphenated command names only for Cline:For a Forge project the names were printed in dotted form (e.g.
speckit.test-ext.hello), but Forge registers its commands hyphenated (speckit-test-ext-hello, viaformat_forge_command_name). So the post-install summary told Forge users to run commands that don't exist under the dotted name.Fix
Extend the existing Cline handling to Forge via
format_forge_command_name. This completes the Forge command-name parity already fixed for hook invocations (#3641) and the init next-steps panel (#3642) — the extension-install listing was the third and last site.Tests
tests/test_extensions.py::test_forge_extension_install_listing_hyphenates_command_names— installs an extension (extension add --dev) in a Forge project and asserts the listing showsspeckit-test-ext-hello, not the dotted form. Fails before the fix; passes after.ruffclean.AI-assisted: authored with Claude Code. Completes the Forge parity series (#3641/#3642) and verified fail-before/pass-after.