source-permalinks

Name: source-permalinks
Availability: InStock
Author: Mozilla

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

1|Updated Mar 17, 2026

Search Tags:#github #citations #specs #source #permalinks #bugzilla #searchfox

Ready to run

npx skills add https://github.com/mozilla/media-skills --skill source-permalinks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-permalinks
Source: https://github.com/mozilla/media-skills/tree/main/source-permalinks
Command: npx skills add https://github.com/mozilla/media-skills --skill source-permalinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create stable, revision-pinned links to source files, specifications, and bug reports instead of fragile trunk or HEAD URLs.

Core Features & Use Cases

Stable Citations: Generate links that remain tied to a specific revision for code review notes, analysis docs, and reports.
Broad Platform Coverage: Works across Searchfox, GitHub, GitLab, googlesource, Codeberg, Chromium, FFmpeg, Bugzilla, and common web standards.
Use Case: When you need to reference a function, spec section, or bug in a write-up, this Skill gives you the correct link format and anchoring style.

Quick Start

Ask the skill to produce revision-pinned permalinks for the source files, spec sections, or bug reports you want to cite.

Frequently Asked Questions about source-permalinks

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

FAQPage Schema

How do I create stable permalinks to source code for citations?▼

To create stable permalinks, you must use revision-pinned URLs tied to a specific commit hash instead of fragile trunk or HEAD links. This ensures your code references remain permanently accessible in analysis docs and reports.

Does permalink generation work with Searchfox and Chromium repositories?▼

Yes, permalink generation works with Searchfox and Chromium repositories, alongside GitHub, GitLab, googlesource, Codeberg, and FFmpeg. It applies the correct anchor formatting and revision resolution for each platform.

Why should I avoid trunk or HEAD links when referencing bug reports?▼

You should avoid trunk or HEAD links because they point to constantly changing code states, causing your references to break over time. Revision-pinned permalinks ensure your bug report citations remain accurate and permanently stable.

What is the best way to pin a GitHub commit URL for code reviews?▼

The best way to pin a GitHub commit URL is to resolve the reference to a specific commit hash and format the link with the correct anchor. This avoids dynamic branch references and provides a stable citation for code review notes.

Can I generate revision-pinned links for web standards and specifications?▼

Yes, you can generate revision-pinned links for web standards and specifications. The process constructs stable URLs that anchor to specific document revisions, ensuring your spec references do not break when the standard updates.

How do I format Bugzilla links to avoid broken citations in analysis docs?▼

To avoid broken citations, Bugzilla links must be constructed using stable, revision-pinned URLs rather than dynamic queries. This anchors the bug report reference to a specific state, keeping your analysis documentation permanently accurate.