github/spec-kit · error · ValidationError

{kind.capitalize()} '{name}' conflicts with core command nam

Error message

{kind.capitalize()} '{name}' conflicts with core command namespace '{namespace}'

What it means

Error "{kind.capitalize()} '{name}' conflicts with core command namespace '{namespace}'" thrown in github/spec-kit.

Source

Thrown at src/specify_cli/extensions/__init__.py:1144

                # 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}'"
                        )

                    if namespace in CORE_COMMAND_NAMES:
                        raise ValidationError(
                            f"{kind.capitalize()} '{name}' conflicts with core command namespace '{namespace}'"
                        )

                if name in declared_names:
                    raise ValidationError(
                        f"Duplicate command or alias '{name}' in extension manifest"
                    )

                declared_names[name] = kind

        return declared_names

    def _get_installed_command_name_map(
        self,
        exclude_extension_id: Optional[str] = None,
    ) -> Dict[str, str]:
        """Return registered command and alias names for installed extensions."""
        installed_names: Dict[str, str] = {}

View on GitHub (pinned to bf88c9f9a8)

Solutions

1. Rename the command/alias so it does not use a core Spec Kit command namespace.

When it happens

Trigger: Thrown at src/specify_cli/extensions/__init__.py:1144 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/411fbef84c1533d7. Report an issue: GitHub.