route-sync

Synchronize feature route maps with current code locations.

Updated May 2, 2026
One-click install
npx skills add https://github.com/GmwEnterprise/route-spec --skill route-sync-gmwenterprise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: route-sync
Source: https://github.com/GmwEnterprise/route-spec/tree/main/skills/route-sync
Command: npx skills add https://github.com/GmwEnterprise/route-spec --skill route-sync-gmwenterprise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature route maps often become outdated as code locations change, leading to wasted time searching for correct files when modifying existing features and increasing the risk of editing incorrect code.

Core Features & Use Cases

  • Route Map Synchronization: Updates feature route map entries when core feature files, entry points, implementation locations, or critical test entries change, only modifying confirmed information and marking unknown fields as uncertain.
  • Outdatedness Auditing: Checks for missing critical location information, non-existent referenced files, or unrecorded feature migrations, with support for both task-specific and full comprehensive audits.
  • Deprecation & Removal Handling: Manages deprecated or deleted features by updating remarks, removing obsolete entries, or archiving entries only when explicitly requested by the user.
  • Use Case: When a core payment processing feature's implementation is migrated from src/payments/legacy/processor.py to src/payments/service/processor.py, this Skill updates the corresponding route map entry to reflect the new location, or marks it as uncertain if the new path is not fully confirmed.

Quick Start

Use the route-sync skill to update the feature route map after migrating the user authentication core implementation to the new auth-service directory.

Frequently Asked Questions about route-sync

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

FAQPage Schema
What is the best way to prevent editing incorrect code when feature locations change?

Preventing edits to incorrect code when feature locations change requires keeping feature route maps aligned with current code location information, ensuring route map entries reflect actual implementation files, entry points, and critical test entry updates.

How do I keep feature route maps updated when implementation files migrate?

Synchronizing feature route maps after implementation file migrations involves updating the corresponding route map entries to reflect new code locations, only modifying confirmed paths and marking unverified fields as uncertain to prevent incorrect file references.

What is a feature route map audit and how does it identify outdated code locations?

A feature route map audit identifies outdated code locations by checking for missing critical location information, non-existent referenced files, and unrecorded feature migrations, supporting both task-specific checks and comprehensive full project reviews.

How do I handle deprecated features in a software documentation audit?

Handling deprecated features in a software documentation audit involves updating remarks, removing obsolete route map entries, or archiving entries, but these actions are strictly executed only when explicitly requested by the user.

Can I update entry points and critical test entries in a route map if the new path is unconfirmed?

Updating entry points and critical test entries with unconfirmed new paths requires marking those specific route map fields as uncertain rather than committing unverified location data, ensuring developers know the information needs validation.

What is the best way to prevent editing incorrect code when feature locations change?

Preventing edits to incorrect code when feature locations change requires keeping feature route maps aligned with current code location information, ensuring route map entries reflect actual implementation files, entry points, and critical test entry updates.