repo-doc-router

Route and organize ClearIntent documentation and repo assets across the repository.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Vel-Labs/ClearIntent --skill repo-doc-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-doc-router
Source: https://github.com/Vel-Labs/ClearIntent/tree/main/skills/repo-doc-router
Command: npx skills add https://github.com/Vel-Labs/ClearIntent --skill repo-doc-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ClearIntent documentation and repo assets often drift when files are moved or renamed. This Skill ensures docs, templates, skills, roadmaps, decisions, and taxonomy stay discoverable by routing and indexing them consistently.

Core Features & Use Cases

  • Document routing: Update references and maintain discoverability after moves.
  • Index maintenance: Refresh doc trees and file inventories to reflect current structure.
  • Governance workflow: Enforce canonical paths, owner handoffs, and validation steps across the repo.

Quick Start

Move the affected docs to their new location and run the governance workflow to refresh references and file trees.

Frequently Asked Questions about repo-doc-router

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

FAQPage Schema
How do I keep documentation discoverable after moving files in a repository?

Documentation discoverability after file moves is maintained by validating references, updating canonical paths in REPO_PROFILE.json, and refreshing the repository file tree and changelog to reflect the new structure.

What is repository document routing and when do I need it?

Repository document routing is the process of updating references and enforcing canonical paths for docs, templates, and roadmaps. You need it when files are moved or renamed to prevent asset drift and maintain governance.

How do I refresh a repository file tree and doc index during migrations?

To refresh a repository file tree and doc index during migrations, move the affected docs to their new location and run the governance workflow to automatically update references and file inventories.

Does this document routing workflow require any external dependencies?

No external dependencies are required. The document routing and index maintenance workflow operates independently to validate references, update REPO_PROFILE.json, and enforce taxonomy governance across the repository.

What's the best way to enforce canonical paths and owner handoffs for repo assets?

The best way to enforce canonical paths and owner handoffs is to apply a governance workflow that validates references across root entrypoints, docs, skills, and templates, ensuring consistent routing and discoverability.

Why does my repository documentation drift after renaming files?

Repository documentation drifts after renaming files because canonical paths and references are not automatically updated, a problem solved by running a governance workflow to validate and refresh the file tree and changelog.