file-links

Format file references into markdown links with GitHub-style line numbers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/benonions/dotfiles --skill file-links
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-links
Source: https://github.com/benonions/dotfiles/tree/main/codex/.codex/skills/community/emacs-skills/file-links
Command: npx skills add https://github.com/benonions/dotfiles --skill file-links

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that when files are referenced, they are consistently formatted as markdown links, including line numbers where applicable, improving clarity and navigability in documentation.

Core Features & Use Cases

  • Consistent Linking: Standardizes the way file paths and line numbers are presented in markdown.
  • GitHub-Style Syntax: Utilizes #L for line numbers and ranges in URLs, mirroring common developer platforms.
  • Use Case: When reporting an error in a code review, you can reference the specific line in a file like [main.py:15](src/main.py#L15) for immediate context.

Quick Start

Format the file reference 'my_script.py' with line 50 as a markdown link.

Frequently Asked Questions about file-links

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

FAQPage Schema
How do I format file references as markdown links with line numbers?

You can format file references as markdown links by using GitHub-style syntax with #L for line numbers and ranges. This standardizes file paths in documentation and code reviews for immediate navigability.

What is the best way to reference a specific line of code in documentation?

The best way to reference a specific line of code is using standardized markdown links. This approach formats file paths with GitHub-style line number syntax, ensuring clear and consistent navigability in your documentation.

Does this markdown link formatting support GitHub-style line ranges?

Yes, the formatting supports GitHub-style line ranges. It utilizes the #L syntax in the URL fragment to denote both single lines and ranges, mirroring common developer platform conventions for precise file locations.

How do I create a markdown link for a code review error report?

To create a markdown link for a code review error report, format the file reference with the specific line number. This provides immediate context by generating a clickable link directly to the exact code location.

Why standardize file path formatting in markdown documentation?

You should standardize file path formatting in markdown documentation to improve clarity and navigability. Consistent linking ensures that file references and line numbers are uniformly presented, making technical documentation easier to traverse.