skills.rest
kriscendobot
kriscendobotCOMMUNITY
Explore all skills by this author →
GitHub

relative paths and links

Enforce relative path conventions across Markdown files and inline code references.

3|2|Updated May 12, 2026
Search Tags:#documentation#markdown#refactoring#links#portability#paths
One-click install
npx skills add https://github.com/kriscendobot/garden --skill relative-paths-and-links
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: relative paths and links
Source: https://github.com/kriscendobot/garden/tree/main/skills/relative-paths
Command: npx skills add https://github.com/kriscendobot/garden --skill relative-paths-and-links

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the issue of broken documentation links caused by hardcoded absolute paths that fail when a repository is cloned or viewed on different machines.

Core Features & Use Cases

  • Path Normalization: Enforces the use of relative paths for internal document references to ensure cross-platform compatibility.
  • Cross-Tree Exception Handling: Provides clear guidelines for when absolute paths are necessary for subagents operating in isolated worktrees.
  • Maintenance Sweeping: Includes a diagnostic command to identify and refactor non-portable absolute paths within the documentation tree.

Quick Start

Run the provided grep command in the terminal to identify all absolute paths in the current directory that require refactoring to relative format.

Frequently Asked Questions about relative paths and links

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

FAQPage Schema
How do I fix broken markdown documentation links caused by hardcoded absolute paths?▼

To fix broken markdown documentation links, you must enforce relative path conventions across the repository. This ensures cross-platform compatibility so links resolve correctly when the repository is cloned or viewed on different machines.

Why do internal documentation links fail when viewing my repository on different developer environments?▼

Internal documentation links fail across developer environments because hardcoded absolute paths are not portable. Enforcing relative paths for internal document references ensures consistent navigation across different machines and web renderers.

What is the best way to refactor absolute paths to relative format in markdown files?▼

The best way to refactor absolute paths to relative format is by running a diagnostic grep command to identify non-portable links in the current directory. This maintenance sweeping identifies all absolute paths requiring refactoring.

When should I use absolute paths instead of relative paths in my documentation?▼

Absolute paths are necessary for subagents operating in isolated worktrees. Cross-tree exception handling provides clear guidelines for when absolute paths are required while maintaining portability for the primary garden structure.

Does standardizing relative paths work with inline code references in markdown?▼

Yes, standardizing relative paths applies to all Markdown files and inline code references. This ensures consistent navigation across different developer environments and web renderers throughout the entire documentation tree.

Related Skills

Explore More Software Engineering Skills→
BaneeishaqueBaneeishaque

VS Code Extension Link Portability

Refactor non-portable extension paths in VS Code settings.json to tilde-based references.

Community
Intermediate
terrylicaterrylica
62

link-validator

Validate markdown links for portability across Claude Code skill deployments.

Community
Basic
bmad-code-orgbmad-code-org
8

bmad-os-audit-file-refs

Audit markdown and YAML files for BMAD file-reference pathing violations.

Official
Advanced
zzafergokzzafergok
1

markdown-to-html-skill

Convert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.

Community
Intermediate