How do I install the Om Fix Specs skill?

Run npx skillmds@latest add open-mercato/om-fix-specs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Om Fix Specs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Om Fix Specs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Om Fix Specs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Om Fix Specs?

open-mercato (@open-mercato) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Om Fix Specs by open-mercato — Agent Skill

Name: Om Fix Specs
Author: open-mercato

Om Fix Specs

Normalize spec filenames in .ai/specs and .ai/specs/enterprise to the date+slug convention. Use this when legacy `SPEC-*` / `SPEC-ENT-*` names need to be cleaned up, when filename collisions appear after dropping numeric prefixes, or when links must be updated after normalization.

open-mercato Updated Sep 17, 2026

File contents

Fix Specs

Normalize legacy spec filenames to the date+slug convention with minimal churn.

When to use

Legacy specs still use SPEC-* or SPEC-ENT-* filename prefixes.
Two specs would collide after removing the numeric prefix.
Links now point to the wrong filename after normalization.

Rules

New canonical filenames are {YYYY-MM-DD}-{slug}.md for both OSS and enterprise specs.
Remove legacy SPEC-* / SPEC-ENT-* filename prefixes instead of inventing replacement numbers.
If two files would normalize to the same target, keep the older filename target and make the newer slug more specific.
Update filename references and links everywhere in the repo.
Preserve document history inside the file content when useful, but filenames MUST follow the date+slug format.

Workflow

Run a dry run first: python3 .ai/skills/om-fix-specs/scripts/fix_spec_conflicts.py --dry-run
Review planned renames and file updates.
Apply changes: python3 .ai/skills/om-fix-specs/scripts/fix_spec_conflicts.py --apply
Verify no conflicts remain: python3 .ai/skills/om-fix-specs/scripts/fix_spec_conflicts.py --dry-run

Notes

The script scans both .ai/specs and ai/specs roots if present.
Enterprise typos are tolerated (enterprise and enterpirse).
Conflict resolution drops legacy numeric prefixes first, then adds a slug suffix only when two files would land on the same target filename.
Files without an embedded YYYY-MM-DD segment are skipped by the script and must be normalized manually.
Review in-file titles manually after normalization if you also want to remove legacy SPEC-* labels from headings.

---name: om-fix-specsdescription: Normalize spec filenames in .ai/specs and .ai/specs/enterprise to the date+slug convention. Use this when legacy `SPEC-*` / `SPEC-ENT-*` names need to be cleaned up, when filename collisions appear after dropping numeric prefixes, or when links must be updated after normalization.---# Fix SpecsNormalize legacy spec filenames to the date+slug convention with minimal churn.## When to use- Legacy specs still use `SPEC-*` or `SPEC-ENT-*` filename prefixes.- Two specs would collide after removing the numeric prefix.- Links now point to the wrong filename after normalization.## Rules1. New canonical filenames are `{YYYY-MM-DD}-{slug}.md` for both OSS and enterprise specs.2. Remove legacy `SPEC-*` / `SPEC-ENT-*` filename prefixes instead of inventing replacement numbers.3. If two files would normalize to the same target, keep the older filename target and make the newer slug more specific.4. Update filename references and links everywhere in the repo.5. Preserve document history inside the file content when useful, but filenames MUST follow the date+slug format.## Workflow1. Run a dry run first: `python3 .ai/skills/om-fix-specs/scripts/fix_spec_conflicts.py --dry-run`2. Review planned renames and file updates.3. Apply changes: `python3 .ai/skills/om-fix-specs/scripts/fix_spec_conflicts.py --apply`4. Verify no conflicts remain: `python3 .ai/skills/om-fix-specs/scripts/fix_spec_conflicts.py --dry-run`## Notes- The script scans both `.ai/specs` and `ai/specs` roots if present.- Enterprise typos are tolerated (`enterprise` and `enterpirse`).- Conflict resolution drops legacy numeric prefixes first, then adds a slug suffix only when two files would land on the same target filename.- Files without an embedded `YYYY-MM-DD` segment are skipped by the script and must be normalized manually.- Review in-file titles manually after normalization if you also want to remove legacy `SPEC-*` labels from headings.

Frequently asked questions