Skip to content

fix: unofficial PyPI warning (#1982) and legacy extension command name auto-correction (#2017)#2027

Open
mbachorik wants to merge 17 commits intogithub:mainfrom
mbachorik:fix/pypi-warning-and-legacy-extension-names
Open

fix: unofficial PyPI warning (#1982) and legacy extension command name auto-correction (#2017)#2027
mbachorik wants to merge 17 commits intogithub:mainfrom
mbachorik:fix/pypi-warning-and-legacy-extension-names

Conversation

@mbachorik
Copy link
Copy Markdown
Contributor

@mbachorik mbachorik commented Mar 30, 2026

Summary

Changes

`docs/installation.md` / `README.md`

  • Warning block clarifying GitHub is the only official source
  • `specify version` verification step added after install instructions

`src/specify_cli/extensions.py`

  • `ExtensionManifest._validate()`: auto-corrects legacy 2-part primary command names (`{ext_id}.cmd` or `speckit.cmd` → `speckit.{ext_id}.cmd`), emitting compatibility warnings; names that cannot be safely corrected still raise `ValidationError`
  • Alias names follow the same correction path via `_try_correct_command_name()` — no separate alias helper
  • Hook `command` refs are rewritten when they point at a renamed command; alias-form refs (`{ext_id}.cmd`) are also canonicalized to `speckit.{ext_id}.cmd`; a warning is emitted whenever any rewrite occurs
  • Individual hook entries validated as dicts — non-mapping entries raise `ValidationError` instead of silently skipping (which would crash `HookExecutor.register_hooks()` later)
  • `_try_correct_command_name()`: static helper covering both `speckit.cmd` and `{ext_id}.cmd` legacy forms for primary commands and aliases

`src/specify_cli/init.py`

  • `extension_add`: prints compatibility warnings from `manifest.warnings` after successful install
  • `extension_remove` confirmation: correct singular/plural (`1 command` vs `N commands`)

`src/specify_cli/agents.py`

  • `CommandRegistrar.unregister_commands()`: removes empty skill parent directories after unlinking SKILL.md files, preventing orphaned `.claude/skills/speckit-*/` dirs

`tests/test_extensions.py`

  • `TestExtensionManifest`: new tests covering primary/alias auto-correction, hook ref rewriting and canonicalization, non-dict hook entry validation
  • `TestCommandRegistrar`: `test_unregister_skill_removes_parent_directory` covering orphaned dir cleanup
  • `TestExtensionRemoveCLI`: CLI tests covering singular/plural command count in removal confirmation

`tests/test_presets.py`

  • `test_search_with_cached_data`: patched to use `unittest.mock.patch` on `get_active_catalogs` to isolate test from live community catalog network calls

Test plan

Unit tests

  • 160 extension tests pass (pytest tests/test_extensions.py)
  • Full suite passes

Live integration tests (real CLI, real filesystem, temp project dir)

All scenarios run against the workspace CLI with actual specify extension add/remove invocations:

Well-formed extension (foobar test extension):

✓ Extension installed successfully!
✓ .specify/extensions/foobar/ exists
✓ 11 command files created in .claude/commands/
✓ No compatibility warnings emitted

Legacy 2-part command name (foobar.hellospeckit.foobar.hello):

✓ Extension installed successfully!
⚠  Compatibility warning: Command name 'foobar.hello' does not follow the required
   pattern 'speckit.{extension}.{command}'. Registering as 'speckit.foobar.hello'.
   The extension author should update the manifest to use this name.
✓ Command file registered under canonical name

Hook with alias-form ref (foobar.hellospeckit.foobar.hello):

✓ Extension installed successfully!
⚠  Compatibility warning: Hook 'after_tasks' referenced command 'foobar.hello';
   updated to canonical form 'speckit.foobar.hello'. The extension author should
   update the manifest.

Non-dict hook entry (install must fail):

Validation Error: Hook 'after_tasks' must be a mapping, got str
✓ Extension not installed (install correctly aborted)

Remove — singular (1 command):

⚠  This will remove:
   • 1 command per agent

Remove — plural (2 commands):

⚠  This will remove:
   • 2 commands per agent

🤖 Generated with Claude Code

@mbachorik mbachorik requested a review from mnriem as a code owner March 30, 2026 21:25
Copilot AI review requested due to automatic review settings March 30, 2026 21:25
…ication (github#1982)

Clarify that only packages from github/spec-kit are official, and add
`specify version` as a post-install verification step to help users
catch accidental installation of an unrelated package with the same name.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves user safety and extension compatibility by warning against unofficial PyPI packages, adding a post-install verification step, and making legacy community extension command names auto-correct (with warnings) instead of hard-failing. It also stabilizes a previously flaky preset-catalog test by preventing unintended live community catalog lookups.

Changes:

  • Add prominent documentation warnings that Spec Kit’s official packages are only distributed from github/spec-kit, plus a recommended specify version verification step.
  • In extension manifest validation, auto-correct common legacy 2-part command names to the required 3-part speckit.{extension}.{command} form and surface compatibility warnings on install.
  • Make TestPresetCatalog::test_search_with_cached_data deterministic by restricting catalogs to default-only via a project-level preset-catalogs.yml.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
README.md Adds an “official source only” warning and a specify version verification step after install instructions.
docs/installation.md Adds the same warning and a verification section recommending specify version.
src/specify_cli/extensions.py Adds command-name regex constant, manifest warnings, and auto-correction logic for legacy command names.
src/specify_cli/__init__.py Prints manifest compatibility warnings after successful specify extension add.
tests/test_extensions.py Adds tests for both auto-correction paths and the no-warning valid path; updates an existing docstring.
tests/test_presets.py Writes .specify/preset-catalogs.yml in a test to avoid community-catalog network flakiness.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

iamaeroplane and others added 2 commits March 30, 2026 23:31
…iling (github#2017)

Community extensions that predate the strict naming requirement use two
common legacy formats ('speckit.command' and 'extension.command').
Instead of rejecting them outright, auto-correct to the required
'speckit.{extension}.{command}' pattern and emit a compatibility warning
so authors know they need to update their manifest. Names that cannot be
safely corrected (e.g. single-segment names) still raise ValidationError.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… network calls

test_search_with_cached_data asserted exactly 2 results but was getting 4
because _get_merged_packs() queries the full built-in catalog stack
(default + community). The community catalog had no local cache and hit
the network, returning real presets. Writing a project-level
preset-catalogs.yml that pins the test to the default URL only makes
the count assertions deterministic.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mbachorik mbachorik force-pushed the fix/pypi-warning-and-legacy-extension-names branch from 56c6b66 to 44d1996 Compare March 30, 2026 21:33
The upstream github#1994 added alias validation in _collect_manifest_command_names,
which also rejected legacy 2-part alias names (e.g. 'speckit.verify').
Extend the same auto-correction logic from _validate() to cover aliases,
so both 'speckit.command' and 'extension.command' alias formats are
corrected to 'speckit.{ext_id}.{command}' with a compatibility warning
instead of hard-failing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings March 30, 2026 21:47
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Copy Markdown
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please address Copilot feedback. If not applicable, please explain why

- _try_correct_command_name: only correct 'X.Y' to 'speckit.ext_id.Y'
  when X matches ext_id, preventing misleading warnings followed by
  install failure due to namespace mismatch
- _validate: add aliases type/string guards matching _collect_manifest
  _command_names defensive checks
- _validate: track command renames and rewrite any hook.*.command
  references that pointed at a renamed command, emitting a warning
- test: fix test_command_name_autocorrect_no_speckit_prefix to use
  ext_id matching the legacy namespace; add namespace-mismatch test
- test: replace redundant preset-catalogs.yml isolation with
  monkeypatch.delenv("SPECKIT_PRESET_CATALOG_URL") so the env var
  cannot bypass catalog restriction in CI environments

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mnriem mnriem self-requested a review March 31, 2026 19:55
Copy link
Copy Markdown
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please address Copilot feedback

@mbachorik
Copy link
Copy Markdown
Contributor Author

@mnriem I've bundled this with the fix for 2/3dot alias notation. Will wait for feedback from the reporter (or we decide tonight and agree on fix). Will address all copilot feedback as usual .. (switching it to draft so it does not spam you)

@mbachorik mbachorik marked this pull request as draft April 1, 2026 11:27
@mbachorik mbachorik force-pushed the fix/pypi-warning-and-legacy-extension-names branch from 3fed7f7 to caee3e0 Compare April 4, 2026 07:34
Copilot AI review requested due to automatic review settings April 4, 2026 07:34
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot AI review requested due to automatic review settings April 4, 2026 15:29
For SKILL.md-based agents (codex, kimi), each command lives in its own
subdirectory (e.g. .agents/skills/speckit-ext-cmd/SKILL.md). The previous
unregister_commands() only unlinked the file, leaving an empty parent dir.

Now attempts rmdir() on the parent when it differs from the agent commands
dir. OSError is silenced so non-empty dirs (e.g. user files) are safely left.

Adds test_unregister_skill_removes_parent_directory to cover this.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mbachorik
Copy link
Copy Markdown
Contributor Author

Fixed (#3067647278). Implemented the cleanup in unregister_commands():

After unlinking SKILL.md, attempts parent.rmdir() when the parent differs from the agent commands dir (i.e. it's a SKILL.md subdirectory, not a flat file). OSError is silenced so non-empty dirs are left untouched. Added test_unregister_skill_removes_parent_directory to cover this. 161 tests pass.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mbachorik mbachorik marked this pull request as ready for review April 11, 2026 09:33
@mbachorik
Copy link
Copy Markdown
Contributor Author

All comments addressed.

@mbachorik mbachorik requested a review from mnriem April 11, 2026 09:34
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 13, 2026

Are we still supporting the original aliasing? We need to give users time to migrate especially since it break extensions. I already reverted that part in an earlier PR, but I do not want to reintroduce the hard change now. We should reserve that for a later date.

Copy link
Copy Markdown
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments above

Aliases are intentionally free-form to preserve community extension
compatibility (e.g. 'speckit.verify' short aliases used by spec-kit-verify
and other existing extensions). This aligns _validate() with the intent of
upstream commit 4deb90f (fix: restore alias compatibility, github#2110/github#2125).

Only type and None-normalization checks remain for aliases. Pattern
enforcement continues for primary command names only.

Updated tests to verify free-form aliases pass through unchanged with
no warnings instead of being auto-corrected.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mbachorik
Copy link
Copy Markdown
Contributor Author

Fixed. Removed alias pattern enforcement from _validate() entirely — aliases are now free-form, matching the intent of your upstream fix in #2125 (4deb90f). Only type and None-normalization checks remain; primary command names still enforce the 3-part speckit.{extension}.{command} pattern.

Verified end-to-end: a spec-kit-verify-style extension with a speckit.verify alias installs, registers (speckit-verify/SKILL.md), and unregisters cleanly with no warnings.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mnriem mnriem self-requested a review April 14, 2026 17:38
Copy link
Copy Markdown
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please address Copilot feedback. Thank you for staying with it!

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves user guidance around unofficial PyPI packages and increases backward compatibility for community extensions by auto-correcting certain legacy command names, while also tightening/covering related behaviors with additional tests.

Changes:

  • Add documentation warnings that the official Spec Kit packages are sourced from github/spec-kit, plus a post-install specify version verification step.
  • Extend extension manifest validation to auto-correct legacy 2-part primary command names and rewrite hook command references, emitting compatibility warnings.
  • Improve uninstall cleanup (remove empty SKILL parent directories) and add/adjust tests, including isolating a previously flaky preset catalog test from network access.
Show a summary per file
File Description
docs/installation.md Adds prominent warning about unofficial PyPI packages and adds a verification step.
README.md Adds the same warning + verification step to the main install instructions.
src/specify_cli/extensions.py Adds manifest.warnings, legacy command auto-correction, and hook command ref rewriting.
src/specify_cli/__init__.py Prints compatibility warnings after extension install and fixes remove confirmation pluralization.
src/specify_cli/agents.py Removes empty SKILL parent directories after unregistering commands.
tests/test_extensions.py Adds coverage for command auto-correction, hook rewriting, SKILL dir cleanup, and removal prompt wording.
tests/test_presets.py Ensures cached-search test is deterministic and isolated from live network catalogs.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 7/7 changed files
  • Comments generated: 1

@mbachorik
Copy link
Copy Markdown
Contributor Author

@mnriem should ok now - there's no additional fix.

@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 14, 2026

@mbachorik Looks like it found one!

@mbachorik
Copy link
Copy Markdown
Contributor Author

it's like a Russian roulette .. looking (before I crash for tonight)

If provides.commands contains a non-mapping entry (e.g. an int or string),
'name' not in cmd raises TypeError instead of a user-facing ValidationError.
Added isinstance(cmd, dict) check at the top of the loop.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mbachorik
Copy link
Copy Markdown
Contributor Author

Fixed comment #3082042943. Added isinstance(cmd, dict) at the top of the command loop — a non-mapping entry (e.g. an int or string) now raises ValidationError: Each command entry in 'provides.commands' must be a mapping instead of letting "name" not in cmd propagate a TypeError.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mbachorik mbachorik requested a review from mnriem April 15, 2026 08:33
@mbachorik
Copy link
Copy Markdown
Contributor Author

@mnriem no new comments from copilot (at least for me).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants