Help us improve
Share bugs, ideas, or general feedback.
From peterpme-skills
Clones a GitHub repo and sets up an interactive study session for reading and analyzing the codebase. Answers questions with source-of-truth evidence from the actual code.
npx claudepluginhub peterpme/skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/peterpme-skills:study-repo <github-url-or-owner/repo> [subpath]<github-url-or-owner/repo> [subpath]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Clone a GitHub repo and interactively explore it for learning. The repo is the source of truth — ground all answers in actual code.
Scouts GitHub repos for patterns, features, and ideas to improve your project by cloning, analyzing architecture and code, comparing with your codebase, and delivering actionable recommendations.
Analyzes GitHub repository source code, generates architecture analysis and quick-start documentation in Chinese. Activates when user provides a repo link and requests code interpretation, architecture analysis, or learning report.
Builds a structured, topic-focused lesson from canonical Entire checkpoints when a developer asks to learn about a specific concept in the repo (e.g., auth, billing webhooks).
Share bugs, ideas, or general feedback.
Clone a GitHub repo and interactively explore it for learning. The repo is the source of truth — ground all answers in actual code.
Accept any of:
https://github.com/owner/repohttps://github.com/owner/repo.gitowner/repoExtract owner and repo from the input.
Target directory: ~/Projects/<repo>
if [ -d ~/Projects/<repo> ]; then
cd ~/Projects/<repo> && git pull
else
gh repo clone <owner>/<repo> ~/Projects/<repo>
fi
If gh is not installed or not authenticated, tell the user to run gh auth login and stop.
On first clone (directory didn't exist before), generate a repo overview:
Show directory tree 1-2 levels deep:
cd ~/Projects/<repo> && fd --max-depth 2 --type f | head -80
Read the README.md (or README) if it exists
Present a concise summary:
On subsequent sessions (directory already existed, git pull ran), check for notes/ directory in the repo and read the most recent notes file to restore context.
If the user provided a subpath argument (e.g., owner/repo src/core), focus the survey and subsequent exploration on that subdirectory.
Source-of-truth policy: Repo-first, knowledge-second
rg and fd within ~/Projects/<repo> to find evidence before answeringsrc/parser.ts:42 uses a recursive descent approach" (repo evidence)Throughout the session, the user may ask to:
Use rg, fd, Read, and Grep tools extensively. Prefer reading actual code over summarizing from memory.
Notes live in ~/Projects/<repo>/notes/*.md — visible to anyone who clones the repo.
At the END of every study session (when the conversation is wrapping up or the user switches topics), automatically save/update study notes:
notes/ directory if it doesn't existnotes/<topic-or-date>.mdWhen starting a session with an already-cloned repo:
notes/ directory exists/study-repo facebook/react
/study-repo https://github.com/jotaijs/jotai
/study-repo solidjs/solid src/reactive