fix(extensions): hyphenate command names in 'extension info' listing - #3744
Merged
mnriem merged 1 commit intoJul 27, 2026
Merged
Conversation
The 'Commands:' section of 'specify extension info' for a locally installed extension printed each command in its manifest dotted form (e.g. speckit.jira.sync). Cline and Forge register hyphenated command names (/speckit-jira-sync), so on those projects the displayed names did not match what the user actually invokes. Format each name through the active agent's command-name formatter, mirroring the parity 'extension add' already applies to its 'Provided commands' listing (github#3669) and completing the Forge/Cline command-name parity from github#3641/github#3642. Adds a regression test asserting the hyphenated form appears (and the dotted form does not) for a Forge project.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates local extension details so Forge and Cline command names match their hyphenated invocation format.
Changes:
- Formats locally installed extension commands for Forge and Cline.
- Adds Forge regression coverage for
extension info.
Show a summary per file
| File | Description |
|---|---|
src/specify_cli/extensions/_commands.py |
Applies active-agent command formatting. |
tests/test_extensions.py |
Verifies Forge command-name hyphenation. |
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.
Problem
The
Commands:section ofspecify extension info(for a locally-installed extension) prints each command in its manifest dotted form, e.g.speckit.jira.sync. Cline and Forge register hyphenated command names (/speckit-jira-sync), so on those projects the names shown byinfodon't match what the user actually invokes.This is the same parity
extension addalready applies to its "Provided commands" listing (#3669), and the same command-name parity fixed for hook invocations (#3641) and the init next-steps panel (#3642) — theinfolisting was simply missed.Fix
Format each command name through the active agent's formatter (
format_cline_command_name/format_forge_command_name), mirroring the exact approach inextension_add. Other agents are unaffected (dotted form retained).Tests
Adds
test_forge_extension_info_hyphenates_command_names: on a Forge project it asserts theinfooutput contains the hyphenatedspeckit-test-ext-helloand not the dottedspeckit.test-ext.hello. Fails on pre-fix code (prints dotted), passes after. Fulltests/test_extensions.py: 385 passed.