一键在 Manus 中运行任何 Skill

librarian

星标532

分支50

更新时间2026年6月5日 16:51

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

sapegin

sapegin/dotfiles

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Choose the workflow

Request	Use
Usage, concepts, best practices	web-search + github clone + read README/docs/examples
Implementation details or source code	github clone + find/grep/read
Change history or rationale	github clone + `git log`, `git blame`, issues/PRs
Broad or ambiguous research	Combine the above

Source workflow

Use github to clone or inspect the repo.
Search locally with find and grep; read relevant files with read.
For history, use git log, git blame, and git show in the clone.
For issues and pull requests, use gh issue, gh pr, or gh search.
Use web-search or web-fetch 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

Permalinks

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

Get a tag SHA when answering version-specific questions:

gh api repos/owner/repo/git/refs/tags/v1.0.0 --jq '.object.sha'

Answer rules

Cite every code-related claim with a permalink.
Prefer official docs and source code over articles.
State uncertainty when evidence is incomplete.
If search fails, broaden terms from exact names to concepts.
Reuse existing clones in /tmp/pi-github-repos/owner/repo.

同仓库更多 Skills

同仓库

agent-comments

sapegin/dotfiles

Scan the current project for agent code comments and fix each one. Use when the user asks to run agent-comments, fix AI comments.

2026-07-04532

fix-pr-ci

sapegin/dotfiles

Fetch the current branch pull request’s CI logs, analyze reported failures, and fix them. Use when asked to investigate failing PR checks, or fix CI failures.

2026-06-29532

review-code

sapegin/dotfiles

Review frontend code changes. Use when reviewing pull requests, examining code changes, or giving feedback on correctness, simplicity, security, performance, tests, and design.

2026-06-26532

grill-me

sapegin/dotfiles

Interview the user relentlessly about a plan, decision, or design until reaching shared understanding. Use when the user wants to stress-test an idea, get grilled on a design, or says “grill me”.

2026-06-26532

grill-in-code

sapegin/dotfiles

Stress-test a plan against the codebase, tests, and existing docs before implementation. Use when the user wants a rigorous, correctness-focused plan review.

2026-06-06532

write-pr-description

sapegin/dotfiles

Write a concise pull request description for the current branch compared to the base branch. Use when preparing pull request text, summarizing branch changes, or drafting a pull request body.

2026-06-06532

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, load and follow the web-search, web-fetch, and github skills.

Choose the workflow

Request	Use
Usage, concepts, best practices	web-search + github clone + read README/docs/examples
Implementation details or source code	github clone + find/grep/read
Change history or rationale	github clone + `git log`, `git blame`, issues/PRs
Broad or ambiguous research	Combine the above

Source workflow

Use github to clone or inspect the repo.
Search locally with find and grep; read relevant files with read.
For history, use git log, git blame, and git show in the clone.
For issues and pull requests, use gh issue, gh pr, or gh search.
Use web-search or web-fetch 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

Permalinks

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

Get a tag SHA when answering version-specific questions:

gh api repos/owner/repo/git/refs/tags/v1.0.0 --jq '.object.sha'

Answer rules

Cite every code-related claim with a permalink.
Prefer official docs and source code over articles.
State uncertainty when evidence is incomplete.
If search fails, broaden terms from exact names to concepts.
Reuse existing clones in /tmp/pi-github-repos/owner/repo.