fix-specs

To standardize legacy spec filenames, you can normalize them to a date+slug format to resolve conflicts and update file references. This process ensures consistency across the repository after migrating to a new naming convention.

Updating in-file references during spec filename normalization is handled automatically by the script. It modifies legacy naming conventions and resolves collisions while updating all internal links to match the new filenames.

The best way to resolve filename collisions during spec document normalization is to keep the older filename and modify the newer one. This conflict resolution mechanism prevents data loss when multiple files share similar legacy names.

Yes, you need Python 3 installed to normalize spec filenames in your repository. The standardization script runs using Python 3 and requires a repository containing spec files that need naming convention updates.

Yes, you can preview spec filename changes by running a dry run before applying them. This allows you to review all filename normalization and reference updates, verifying accuracy before committing the changes.

You should use a filename normalization script for spec documents after migrating to a new naming convention. It is specifically designed to update all references to new filenames when dealing with legacy naming formats like SPEC- or SPEC-ENT- prefixes.