fix-specs

Normalize legacy SPEC-* and SPEC-ENT-* filenames to date+slug convention.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/TomekNocon/open-logistico --skill fix-specs-tomeknocon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-specs
Source: https://github.com/TomekNocon/open-logistico/tree/main/.ai/skills/fix-specs
Command: npx skills add https://github.com/TomekNocon/open-logistico --skill fix-specs-tomeknocon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Legacy SPEC-* and SPEC-ENT-* filenames create inconsistency, broken links, and collisions when numeric prefixes are removed. This Skill standardizes names to a date+slug convention to improve discoverability and history preservation.

Core Features & Use Cases

  • Normalize legacy SPEC-* / SPEC-ENT-* prefixes to the date+slug format.
  • Resolve collisions by keeping the older canonical target or appending a slug suffix.
  • Update all internal references and links across the repository to reflect new filenames.

Quick Start

Run the fix-specs script to normalize all legacy SPEC-* filenames to the date+slug convention.

Frequently Asked Questions about fix-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I normalize legacy spec filenames to a date+slug convention?▼

To normalize legacy spec filenames, run the fix-specs script to convert SPEC-* and SPEC-ENT-* prefixes into the canonical date+slug.md format. It restores repository consistency and updates all internal references automatically.

What happens when filename collisions occur after removing numeric prefixes from specs?▼

When filename collisions occur during spec normalization, the script resolves them by keeping the older canonical target or appending a slug suffix. This ensures date+slug naming consistency without overwriting existing repository files.

How are broken internal links handled when renaming repository spec files?▼

Broken internal links are handled by updating all internal references throughout the repository to reflect the new date+slug filenames. This maintains link integrity across both OSS and enterprise specs directories during normalization.

Can I use this to normalize spec filenames in both OSS and enterprise directories?▼

Yes, you can normalize spec filenames in both OSS and enterprise directories. The script applies the date+slug convention to both specs directories, dropping legacy SPEC-ENT-* and SPEC-* prefixes while resolving any naming conflicts.

Why do legacy spec filenames cause broken links and collisions in a repository?▼

Legacy spec filenames cause broken links and collisions because their numeric prefixes create inconsistency when removed. Normalizing to a date+slug convention improves discoverability, preserves history, and restores link integrity across the repository.