librarian

To get GitHub permalinks for open-source library research, the Skill clones repositories, searches for identifiers, inspects files, and resolves commit SHAs to construct stable blob links for every code-related claim. It generates verifiable citations pointing to precise lines.

To find why behavior changed in a repository's git log, the Skill uses a request-aware workflow to research historical context. It inspects commit history and source files, then extracts evidence with verifiable GitHub permalinks to show exactly what implementation lines were modified.

The best way to do an implementation deep dive is using a workflow that targets conceptual usage and implementation details. It clones the repository, searches for specific identifiers, inspects files, and generates stable GitHub blob links to cite the exact source lines.

Yes, you can get code-cited answers for conceptual usage questions. The Skill selects a request-aware strategy to research open-source repos, extracting evidence from specific files and lines to produce answers grounded in actual library code with permanent GitHub citations.

No, source inspection for repo research requires no external dependencies. The Skill handles the entire process internally by sequentially executing tools to clone repositories, resolve commit SHAs, and construct verifiable GitHub permalinks for implementation analysis.

A limitation of using automated permalinks for code citation is that the Skill relies on sequential tool execution, repo cloning, and code search. It requires resolving commit SHAs to construct stable blob links, meaning it targets open-source repositories and specific files rather than private codebases.