Formats file references as markdown links with GitHub-style line number anchors.
npx skills add https://github.com/hdeshev/pi-config --skill file-links-hdeshev
Please help me install this Agent Skill. Skill: file-links Source: https://github.com/hdeshev/pi-config/tree/main/agent/skills/emacs-file-links Command: npx skills add https://github.com/hdeshev/pi-config --skill file-links-hdeshev
#L fragments for single lines and #L42-L50 style fragments for line ranges. - Consistent Link Text: Keeps the link text readable with filename:line notation while the URL carries the anchor. - Use Case: When reviewing code, the assistant outputs [parser.el:42-50](src/parser.el#L42-L50) so you can jump directly to the referenced block. ## Quick Start Ask the assistant to reference the files it modified, and it will format each one as a clickable markdown link with the relevant line numbers.High-intent search queries and answers about installing and using this skill.
Format them as markdown links with the path relative to the project root, such as [filename.el](path/to/filename.el). Add a #L fragment to the URL when a specific line number is relevant.
Use the #L start-end fragment syntax, for example filename.el#L42-L50 for lines 42 through 50. The link text should mirror the range as filename.el:42-50 so it stays readable.
The #L fragment syntax is GitHub-style but is also recognized by editors and tools that resolve such links, including Emacs configurations set up for it. Plain markdown viewers will still render a working file link without line jumping.
Include line numbers when they add context, such as error locations, function definitions, or modified lines. Omit them when referring to the file as a whole, since stale line numbers can mislead after edits.
A common mistake is putting the #L anchor in the link text but not the URL, or mismatching the range between them. The range must appear in both the link text (with a colon and dash) and the URL (with #L and -L).
dubwoahAnswer codebase questions via read-only Grep, Glob, and file reads with cited paths.
mthinesApply code review comments by editing code or generating implementation plans.
opensage-agentLocate code symbol definitions in containerized environments using ctags indexing.
simorgh3196Navigate Rust codebases using LSP-based symbol resolution.