القائمة
Use when you need to fetch a GitHub repo's metadata, README, and file tree — wraps gh CLI. Returns structured data. Also use for "check this repo", "what is this repo", or "fetch repo info".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when you need to commit and push changes — stages files, commits with co-author tags, pulls with rebase, resolves conflicts, and pushes. Also supports "pr" mode for creating PRs and "clean" mode for pruning merged branches. Also use for "commit", "push", "sync", or "create PR".
Use when the user wants short-and-sweet answers to one or more questions. Restates each question as a bold heading, then answers in 2–5 lines per question. Bullets and small tables allowed when they help. Also use for "quick question", "qq", "answer briefly", or any "/my-qq <question>" invocation.
Use when starting implementation on any project — reads planning docs, dispatches sub-agents, and creates or reiterates docs/acceptance-criteria.md with measurable criteria per feature. Must run before writing implementation code. Also use for "create acceptance criteria", "what are the requirements", or "define done".
Use when starting a new feature or project from a raw idea — asks targeted questions and produces a structured PRD at docs/prd-<slug>.md. Sits upstream of /my-prompt. Also use for "write a PRD", "product requirements", or "what should we build".
Use when code needs rigorous review before shipping — spawns skeptic/believer/referee agents in iterative rounds until findings converge to nitpicks. Use after implementing features, before merging PRs, or when the user asks for a "thorough review", "adversarial review", or "tear this apart".
Use when facing a complex task that benefits from multiple specialized agents working in parallel — spawns, delegates, tracks status, and collects results. Also use when the user says "use agents", "multi-agent", or "parallelize this".
| name | my-fetch-repo |
| description | Use when you need to fetch a GitHub repo's metadata, README, and file tree — wraps gh CLI. Returns structured data. Also use for "check this repo", "what is this repo", or "fetch repo info". |
| argument-hint | < owner/repo | GitHub URL > |
Fetches repo metadata, README content, and file tree using gh CLI. Returns structured data for standalone use or as input to /my-research-targets pipeline.
gh CLI installed and authenticated (gh auth status)/my-fetch-repo https://github.com/owner/repo — fetch and display/my-fetch-repo owner/repo — fetch by owner/repo/my-research-targets for GitHub URLsgh repo view <owner>/<repo> --json name,description,stargazerCount,forkCount,licenseInfo,primaryLanguage,topics,url,createdAt,updatedAt
gh api repos/<owner>/<repo>/readme --jq '.content' | base64 -d | head -200
gh api 'repos/<owner>/<repo>/git/trees/main?recursive=1' --jq '.tree[] | select(.type=="blob") | .path' | head -80
If gh fails (rate limit, private repo):
WebFetch "https://github.com/<owner>/<repo>" with prompt "Extract repo description, stars, language, and README summary"
## owner/repo
Stars: 12,345 | License: MIT | Language: TypeScript
Topics: agent, cli, mcp
Created: 2025-06-15 | Updated: 2026-03-18
### README (first 200 lines)
<readme content>
### File Tree (top 80 files)
<file paths>
When called by /my-research-targets, return raw data for classification.
gh api has rate limits (5000/hr authenticated) — batch requests when fetching multiple reposmain branch by default — some repos use master; fallback: gh api repos/<owner>/<repo> --jq '.default_branch'gh auth status before first use in a session