fix-specs

Detect and resolve duplicate SPEC or SPEC-ENT numbers in documentation.

1.6k|354|Updated Sep 10, 2025
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill fix-specs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-specs
Source: https://github.com/open-mercato/open-mercato/tree/main/.ai/skills/fix-specs
Command: npx skills add https://github.com/open-mercato/open-mercato --skill fix-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically detects and resolves conflicts in spec numbering within documentation, ensuring consistency and preventing broken links.

Core Features & Use Cases

  • Conflict Detection: Identifies duplicate SPEC or SPEC-ENT numbers.
  • Automated Renumbering: Moves the newest conflicting spec to the end of the sequence with minimal disruption.
  • Reference Updates: Automatically updates internal links and references to point to the correct, renumbered specs.
  • Use Case: When a new specification is added that accidentally uses an existing number, this skill can fix it without requiring manual searching and updating of all related documents.

Quick Start

Run a dry run of the fix-specs skill to see planned changes.

Frequently Asked Questions about fix-specs

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

FAQPage Schema
How do I resolve duplicate spec numbers in documentation?

Duplicate spec numbers in documentation are resolved by detecting conflicting SPEC or SPEC-ENT identifiers, renumbering the newest file to the end of the sequence, and automatically updating all internal references and links to maintain consistency.

What is the best way to update internal links after renumbering specs?

The best way to update internal links after renumbering specs is to use an automated script that detects duplicate spec numbers, renumbers the newest conflicting file, and automatically updates all internal references and links to prevent broken documentation paths.

Does spec conflict resolution work with both OSS and enterprise identifiers?

Spec conflict resolution supports both OSS and enterprise identifiers, including enterprise-specific SPEC-ENT numbers. It preserves staged spec variants and handles directory name typos while renumbering conflicting documentation files.

How does automated renumbering decide which spec to move?

Automated renumbering decides which spec to move by prioritizing dated filenames to identify the newest conflicting spec. When dated filenames are unavailable, it falls back to using file modification time for conflict resolution.

Can I preview documentation changes before fixing spec conflicts?

You can preview documentation changes before fixing spec conflicts by running a dry run. This shows all planned renumbering and reference update changes without permanently modifying your actual spec files and internal links.

What happens to staged spec variants during conflict renumbering?

Staged spec variants are preserved during conflict renumbering. The process maintains staged variants while moving the newest conflicting spec identifier to the end of the sequence and automatically updating internal references and links.