fix-specs

Normalize legacy SPEC-* filenames to date+slug convention in spec directories.

1|2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/matchojecki/logistiko-celny --skill fix-specs-matchojecki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-specs
Source: https://github.com/matchojecki/logistiko-celny/tree/main/.ai/skills/fix-specs
Command: npx skills add https://github.com/matchojecki/logistiko-celny --skill fix-specs-matchojecki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Legacy SPEC-* and SPEC-ENT-* spec filenames clutter repositories and break links after normalization. This Skill provides a safe, automated way to rename these files to the date+slug convention, preserving history and updating internal references where possible.

Core Features & Use Cases

  • Automatic detection of legacy SPEC-* patterns in .ai/specs and ai/specs directories.
  • Safe renaming with dry-run and apply modes, plus update of in-text links referencing old filenames.
  • Conflict resolution for collisions by preferring older targets and making newer slugs more specific.
  • Optional script-based workflow to audit and apply changes across large codebases.

Quick Start

Run the normalization workflow to rename legacy SPEC-* filenames to the date+slug convention while preserving history.

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 and slug convention?

You can normalize legacy spec filenames by running an automated renaming workflow that detects SPEC-* prefixes in .ai/specs or ai/specs directories and converts them to a date+slug convention. It includes a dry-run mode to safely preview changes before applying them.

How do I update in-text references when renaming spec files in bulk?

When renaming spec files in bulk, the normalization workflow automatically detects and updates in-text references pointing to old filenames. This ensures internal documentation remains consistent and prevents broken links across your codebase after the rename.

What happens if multiple legacy spec files normalize to the same date and slug?

If filename collisions occur during normalization, the workflow resolves them by preferring the older target file and making the newer file's slug more specific. This conflict resolution mechanism ensures no specs are overwritten during the batch renaming process.

Can I preview spec filename changes before applying them to my repository?

Yes, you can preview spec filename changes using the built-in dry-run mode. The rename planner generates a full audit of proposed normalization changes, allowing you to verify the date+slug conversions and reference updates before committing them to your repository.

Does the spec normalization workflow handle both OSS and enterprise spec directories?

Yes, the spec normalization workflow handles both OSS and enterprise spec directories. It automatically detects legacy SPEC-* and SPEC-ENT-* patterns within .ai/specs and ai/specs paths to restore consistent naming across different project environments.