菜单
Gather and summarize information about a GitHub or Gitea repository — README, docs, examples, structure, and key stats. Use when user wants to learn about a repo, understand a project, or explore a library before using it.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | view-repo |
| description | Gather and summarize information about a GitHub or Gitea repository — README, docs, examples, structure, and key stats. Use when user wants to learn about a repo, understand a project, or explore a library before using it. |
| argument-hint | <owner/repo or URL> |
| allowed-tools | Bash(gh repo *), Bash(gh api *), Agent, mcp__github__get_file_contents, mcp__github__search_code, mcp__github__list_releases, mcp__github__list_branches, mcp__gitea__* |
Gather and summarize key information about a repository.
View the repository specified by $ARGUMENTS (an owner/repo string or full URL).
github.com or is just owner/repo → use gh CLI / GitHub MCP# Basic info
gh repo view $ARGUMENTS
# File tree (top-level + key dirs)
gh api repos/$ARGUMENTS/contents/ --jq '.[].name'
Use equivalent Gitea MCP tools to fetch repo details and file listing.
Fetch these if they exist:
docs/, doc/, documentation/ dirsexamples/, example/, _examples/ dirsFor GitHub:
# Read a file
gh api repos/$ARGUMENTS/contents/README.md --jq '.content' | base64 -d
# List a directory
gh api repos/$ARGUMENTS/contents/docs --jq '.[].name'
Or use mcp__github__get_file_contents for individual files.
# Recent releases
gh release list --repo $ARGUMENTS --limit 3
# Recent activity
gh api repos/$ARGUMENTS/commits --jq '.[0:3] | .[] | .commit.message'
# Stars, forks, issues
gh repo view $ARGUMENTS --json stargazerCount,forkCount,openIssues
Description: one-line summary Language: primary language | License: license | Stars: count
2-3 sentences explaining the project's purpose and scope.
The shortest path to using this — from the README or examples.
Brief description of how the repo is organized (key directories and their purpose).
Links or pointers to available docs, guides, and examples.
Latest release, recent commits, maintenance status.
Anything surprising, important caveats, or useful context.
Generate a single-file HTML artifact (status report, slide deck, prototype, throwaway editor, flowchart, etc.) and open it in the browser. Use when the user wants a one-off visual artifact instead of markdown — for sharing, reference, or interactive exploration.
Gather context from the codebase and (optionally) the web, then propose multiple ways to move forward with tradeoffs, relative impact, and effort. Use when user wants to explore options, weigh approaches, or asks "what are my options" / "how should I tackle this" before committing to a plan.
Propose a concrete plan to cut a branch and implement a change as one or more atomic commits, grounded in the current codebase and (optionally) outside research. Use when user wants a step-by-step implementation plan, asks "propose a plan" / "how would you implement this", or is ready to move from discussion to execution.
Summarize what shipped over a date range, commit range, or release tag — synthesizes git log, GitHub PRs, and Linear issues into a single markdown brief.
View a Sentry issue by short ID (e.g. PROJECT-123) or URL. Shows details, status, latest event, and tag distribution. Use when user wants to view, check, or look up a Sentry issue, error, or event.
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.