github/spec-kit · error · ValidationError
Invalid {kind} {name!r}: {path_reason}
Error message
Invalid {kind} {name!r}: {path_reason} What it means
Error "Invalid {kind} {name!r}: {path_reason}" thrown in github/spec-kit.
Source
Thrown at src/specify_cli/extensions/__init__.py:1123
if aliases is None:
aliases = []
if not isinstance(aliases, list):
raise ValidationError(
f"Aliases for command '{primary_name}' must be a list"
)
for kind, name in [("command", primary_name)] + [
("alias", alias) for alias in aliases
]:
if not isinstance(name, str):
raise ValidationError(
f"{kind.capitalize()} for command '{primary_name}' must be a string"
)
path_reason = relative_extension_path_violation(name)
if path_reason:
raise ValidationError(
f"Invalid {kind} {name!r}: {path_reason}"
)
# Enforce canonical pattern only for primary command names;
# aliases are free-form to preserve community extension compat.
if kind == "command":
match = EXTENSION_COMMAND_NAME_PATTERN.match(name)
if match is None:
raise ValidationError(
f"Invalid {kind} '{name}': "
"must follow pattern 'speckit.{extension}.{command}'"
)
namespace = match.group(1)
if namespace != manifest.id:
raise ValidationError(
f"{kind.capitalize()} '{name}' must use extension namespace '{manifest.id}'"
)View on GitHub (pinned to bf88c9f9a8)
Solutions
- Fix the command or alias path/name in the extension manifest according to the reported reason (e.g. no '..' segments, valid characters).
When it happens
Trigger: Thrown at src/specify_cli/extensions/__init__.py:1123 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of github/spec-kit@bf88c9f9a8 (2026-08-14).
Data as JSON: /api/errors/2eeeeb5e8d501fe0.
Report an issue: GitHub.