skills.rest
alastor0325
alastor0325COMMUNITY
Explore all skills by this author →
WebsiteGitHub

source-links

Hyperlink cited files, functions, lines, specs, and documents to public URLs.

Updated Jun 3, 2026
Search Tags:#documentation#references#specs#source-links#hyperlinks#pinned-urls
One-click install
npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill source-links
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-links
Source: https://github.com/alastor0325/fx-bug-toolkit/tree/main/skills/source-links
Command: npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill source-links

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When documenting or discussing code and standards, this rule ensures every reference is clickable, reliable, and resilient to codebase movement by enforcing hyperlinking to public URLs.

Core Features & Use Cases

  • Always hyperlink referenced files, functions, lines, specs, and other web resources.
  • Prefer revision-pinned URLs to prevent link rot; fall back to stable URLs if pinning isn't available.
  • Maintain consistent anchor text and avoid plain-text citations in outputs.
  • Use Case: In a Firefox debugging report, replace all mentions of a file or spec with a linked source.

Quick Start

Always replace any cited file, function, line, spec, or document with a clickable, revision-pinned URL.

Frequently Asked Questions about source-links

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

FAQPage Schema
How do I hyperlink cited sources with pinned URLs in technical documentation?▼

To hyperlink cited sources with pinned URLs, replace plain-text references to files, functions, and specs with clickable, revision-pinned public URLs. This ensures documentation references remain reliable and resilient to codebase movement.

What's the best way to prevent link rot when referencing Firefox code components?▼

Preventing link rot when referencing Firefox code components requires enforcing revision-pinned URLs for all cited files and functions. If revision pinning is unavailable, fall back to stable URLs to maintain link integrity across codebase updates.

How do I replace plain-text citations with clickable links in a debugging report?▼

To replace plain-text citations with clickable links in a debugging report, apply hyperlinking rules that convert all mentioned files, lines, and specs into public URLs with consistent anchor text, eliminating unlinked references entirely.

When do I need revision-pinned URLs for source code references?▼

You need revision-pinned URLs for source code references when preparing investigations or technical documentation that cites code across components. Pinning ensures the referenced code state remains accurate and accessible despite ongoing repository changes.

Can I use stable URLs instead of revision-pinned links for spec citations?▼

You can use stable URLs instead of revision-pinned links for spec citations only when pinning is not available. Stable URLs serve as a fallback to maintain clickable references, though revision-pinned URLs are preferred for accuracy.

Related Skills

Explore More Software Engineering Skills→
mozillamozilla

source-permalinks

Construct revision-pinned permalinks for source code, specs, and bug reports.

Official
Basic
a-tabijia-tabiji

validate-links

Identify and fix broken hyperlinks across HTML content.

Community
Intermediate
KrystianYCSilvaKrystianYCSilva

markdown-expert

Create Markdown documentation with Mermaid diagrams and GFM tables.

Community
Intermediate
JGalegoJGalego
6

bluff

Verify URLs and non-URL citations in AI-generated text for resolution status.

Community
Intermediate