Explore and compare multi-repository codebases across GitHub, npm, PyPI, and crates.
npx skills add https://github.com/stevoland/dotfiles --skill librarian-stevoland
Please help me install this Agent Skill. Skill: librarian Source: https://github.com/stevoland/dotfiles/tree/main/opencode/skill/librarian Command: npx skills add https://github.com/stevoland/dotfiles --skill librarian-stevoland
This skill enables deep cross-repo codebase exploration to understand architecture and identify patterns across libraries and projects.
Start by asking the Librarian to explore a repository by name (e.g., vercel/ai) and provide a high-level architecture overview plus a cross-repo comparison.
High-intent search queries and answers about installing and using this skill.
To explore multi-repo codebases for architecture patterns, you can request a high-level overview of a repository by name and then perform a cross-repo comparison to map implementation differences and relationships across ecosystems.
Yes, you can compare library internals across GitHub, npm, PyPI, and crates by analyzing how competing implementations are structured and tracing design decisions across different package ecosystems.
Cross-repo codebase exploration is useful for evaluating competing implementations, understanding library internals, identifying architecture patterns, and tracing design decisions across multiple projects and ecosystems.
You analyze implementation differences by providing repository names to explore, which generates a high-level architecture overview and maps relationships, usage patterns, and structural variations across the specified codebases.
You need multi-repo pattern analysis when evaluating competing library implementations, tracing architectural design decisions across ecosystems, or mapping usage relationships across multiple repositories before making technical adoption choices.
Comparing codebases across different package ecosystems requires providing accurate repository names and relies on available source code for mapping architecture, meaning private or inaccessible repositories may limit the depth of cross-repo analysis.
KhoiwallFetch source code from npm, PyPI, crates.io, and GitHub/GitLab repositories.
VanLengsMap business domains, boundaries, and interactions into a formal domain canvas document.
juanjaragaviLocate and map code implementations, dependencies, and relationships across large codebases.
ajoslinExplore multi-repo codebases across GitHub, npm, PyPI, and crates to map library architecture.
