メニュー
Research open-source libraries with evidence-backed answers and GitHub permalinks. Use when the user asks about library internals, implementation details, source code references, change history, or authoritative answers backed by actual code.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/sapegin/dotfiles --skill librarianコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Review a diff for local code quality, AI-generated slop, and polish in application code, configuration, documentation, and agent artifacts.
Review a diff for requirements, behavior, APIs, architecture, and maintainability across code, configuration, documentation and agent artifacts.
Audit every local skill for predictable behavior, sound structure, and prompt quality.
SOC 職業分類に基づく
SKILL.md を表示中
| name | librarian |
| description | Research open-source libraries with evidence-backed answers and GitHub permalinks. Use when the user asks about library internals, implementation details, source code references, change history, or authoritative answers backed by actual code. |
Research open-source libraries by finding evidence in code, docs, issues, pull requests, and history. Back code-related claims with GitHub permalinks.
When needed, use the web_search and web_fetch tools, and load and follow the github skill.
| Request | Use |
|---|---|
| Usage, concepts, best practices | web_search + github skill + read README/docs/examples |
| Implementation details or source code | github skill + find/grep/read |
| Change history or rationale | github skill + git log, git blame, issues/PRs |
| Broad or ambiguous research | Combine the above |
git log, git blame, and git show in the clone.gh issue, gh pr, or gh search.web_search or web_fetch tools for non-GitHub docs, articles, and discussions when useful.Common commands:
cd /tmp/pi-github-repos/owner/repo
# Get the exact commit for permalinks
git rev-parse HEAD
# Find recent changes to a file
git log --oneline -n 20 -- path/to/file.ts
# See who last changed specific lines
git blame -L 10,30 path/to/file.ts
# Inspect a commit's changes to a file
git show <sha> -- path/to/file.ts
# Search related GitHub issues and merged PRs
gh search issues "keyword" --repo owner/repo --state all --limit 10
gh search prs "keyword" --repo owner/repo --state merged --limit 10
Use full commit SHAs, not branch names:
https://github.com/<owner>/<repo>/blob/<commit-sha>/<filepath>#L<start>-L<end>
Get the current clone SHA:
cd /tmp/pi-github-repos/owner/repo && git rev-parse HEAD
Resolve a tag to its commit SHA when answering version-specific questions:
gh api repos/owner/repo/commits/v1.0.0 --jq '.sha'
Do not use the tag ref’s .object.sha; annotated tags return a tag-object SHA rather than the commit needed for a source permalink.
/tmp/pi-github-repos/owner/repo.