메뉴
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 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Scan the current project for agent code comments and fix each one. Use when the user asks to run agent-comments, fix AI comments.
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.
Review frontend code changes. Use when reviewing pull requests, examining code changes, or giving feedback on correctness, simplicity, security, performance, tests, and design.
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”.
Stress-test a plan against the codebase, tests, and existing docs before implementation. Use when the user wants a rigorous, correctness-focused plan review.
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.
| 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.
| 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 |
git log, git blame, and git show in the clone.gh issue, gh pr, or gh search.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
Get a tag SHA when answering version-specific questions:
gh api repos/owner/repo/git/refs/tags/v1.0.0 --jq '.object.sha'
/tmp/pi-github-repos/owner/repo.