[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72D8FJ5NEBYY16WM7CDQKY2":3,"skill-same:01M72D8FJ5NEBYY16WM7CDQKY2":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72D8FJ5NEBYY16WM7CDQKY2","repo-recap",null,"Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass \"en\" or \"fr\" as argument for language (default fr).","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Frepo-recap\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\ndescription: Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass \"en\" or \"fr\" as argument for language (default fr).\nallowed-tools: Bash Read Grep\n---\n\n# Repo Recap\n\nGenerate a structured recap of the repository state: open PRs, open issues, recent releases, and executive summary. Output is formatted as Markdown with clickable GitHub links, ready to share.\n\n## Language\n\n- Check the argument passed to this skill\n- If `en` or `english` → produce the recap in English\n- If `fr`, `french`, or no argument → produce the recap in French (default)\n\n## Preconditions\n\nBefore gathering data, verify:\n\n```bash\n# Must be inside a git repo\ngit rev-parse --is-inside-work-tree\n\n# Must have gh CLI authenticated\ngh auth status\n```\n\nIf either fails, stop and tell the user what's missing.\n\n## Steps\n\n### 1. Gather Data\n\nRun these commands in parallel via `gh` CLI:\n\n```bash\n# Repo identity (for links)\ngh repo view --json nameWithOwner -q .nameWithOwner\n\n# Open PRs with metadata\ngh pr list --state open --limit 50 --json number,title,author,createdAt,changedFiles,additions,deletions,reviewDecision,isDraft\n\n# Open issues with metadata\ngh issue list --state open --limit 50 --json number,title,author,createdAt,labels,assignees\n\n# Recent releases (for version history)\ngh release list --limit 5\n\n# Recently merged PRs (for contributor activity)\ngh pr list --state merged --limit 10 --json number,title,author,mergedAt\n```\n\nNote: `author` in JSON results is an object `{login: \"...\"}` — always extract `.author.login` when processing.\n\n### 2. Determine Maintainers\n\nTo distinguish \"our PRs\" from external contributions:\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fcollaborators --jq '.[].login'\n```\n\nIf this fails (permissions), fallback: authors with write\u002Fadmin access are those who merged PRs recently. When in doubt, ask the user.\n\n### 3. Analyze and Categorize\n\n#### PRs — Categorize into 3 groups:\n\n**Our PRs** (author is a repo collaborator):\n- List with PR number (linked), title, size (+additions, files count), status\n\n**External — Reviewable** (manageable size, no major blockers):\n- Additions ≤ 1000 AND files ≤ 10\n- No merge conflicts, CI not failing\n- Include: PR link, author, title, size, review status, recommended action\n\n**External — Problematic** (any of: too large, CI failing, overlapping, merge conflict):\n- Additions > 1000 OR files > 10\n- OR CI failing (reviewDecision = \"CHANGES_REQUESTED\" or checks failing)\n- OR touches same files as another open PR (= overlap)\n- Include: PR link, author, title, size, specific problem, action taken\u002Fneeded\n\n**Size labels** (use in \"Taille\" column for quick visual triage):\n\n| Label | Additions |\n| ----- | --------- |\n| XS | \u003C 50 |\n| S | 50-200 |\n| M | 200-500 |\n| L | 500-1000 |\n| XL | > 1000 |\n\nFormat: `+{additions}, {files} files ({label})` — e.g., `+245, 2 files (S)`\n\n#### Detect overlaps:\nTwo PRs overlap if they modify the same files. Use `changedFiles` from the JSON data. If >50% file overlap between 2 PRs, flag both as overlapping and cross-reference them.\n\n#### Flag clusters:\nIf one author has 3+ open PRs, note it as a \"cluster\" with suggested review order (smallest first, or by dependency chain).\n\n#### Issues — Categorize by status:\n- **In progress**: has an associated open PR (match by PR body containing `fixes #N`, `closes #N`, or same topic)\n- **Quick fix**: small scope, actionable (bug reports, small enhancements)\n- **Feature request**: larger scope, needs design discussion\n- **Covered by PR**: an existing PR addresses this issue (link it)\n\n### 4. Derive Recent Releases\n\nFrom `gh release list` output, extract version, date, and name. List the 5 most recent.\n\nIf no releases found, check merged PRs for release-please pattern (title matching `chore(*): release *`) as fallback.\n\n### 5. Executive Summary\n\nProduce 5-6 bullet points:\n- Total open PRs and issues count\n- Active contributors (who has the most PRs\u002Fissues)\n- Main risks (oversized PRs, CI failures, merge conflicts)\n- Quick wins (small PRs ready to merge — XS\u002FS size, no blockers)\n- Bug fixes needed (hook bugs, regressions)\n- Our own PRs status\n\n### 6. Format Output\n\nStructure the full recap as Markdown with:\n- `# {Repo Name} — Récap au {date}` as title (FR) or `# {Repo Name} — Recap {date}` (EN)\n- Sections separated by `---`\n- All PR\u002Fissue numbers as clickable links: `[#123](https:\u002F\u002Fgithub.com\u002F{owner}\u002F{repo}\u002Fpull\u002F123)` for PRs, `...\u002Fissues\u002F123` for issues\n- Tables with Markdown pipe syntax for all listings\n- Bold for emphasis on actions and risks\n- Cross-references between related PRs and issues (e.g., \"Covered by [#131](link)\")\n\n**Empty data handling**:\n- 0 open PRs → display \"Aucune PR ouverte.\" (FR) or \"No open PRs.\" (EN) instead of empty table\n- 0 open issues → display \"Aucune issue ouverte.\" (FR) or \"No open issues.\" (EN)\n- 0 releases → display \"Aucune release récente.\" (FR) or \"No recent releases.\" (EN)\n\n### 7. Copy to Clipboard\n\nAfter displaying the recap, automatically copy it to clipboard:\n\n```bash\n# Cross-platform clipboard\nclip() {\n  if command -v pbcopy &>\u002Fdev\u002Fnull; then pbcopy\n  elif command -v xclip &>\u002Fdev\u002Fnull; then xclip -selection clipboard\n  elif command -v wl-copy &>\u002Fdev\u002Fnull; then wl-copy\n  else cat\n  fi\n}\n\ncat \u003C\u003C 'EOF' | clip\n{formatted recap content}\nEOF\n```\n\nConfirm with: \"Copié dans le presse-papier.\" (FR) or \"Copied to clipboard.\" (EN)\n\n## Output Template (FR)\n\n```markdown\n# {Repo Name} — Récap au {date}\n\n## Releases récentes\n\n| Version | Date | Highlights |\n| ------- | ---- | ---------- |\n| ...     | ...  | ...        |\n\n---\n\n## PRs ouvertes ({count} total)\n\n### Nos PRs\n\n| PR | Titre | Taille | Status |\n| -- | ----- | ------ | ------ |\n\n### Contributeurs externes — Reviewables\n\n| PR | Auteur | Titre | Taille | Status | Action |\n| -- | ------ | ----- | ------ | ------ | ------ |\n\n### Contributeurs externes — Problématiques\n\n| PR | Auteur | Titre | Taille | Problème | Action |\n| -- | ------ | ----- | ------ | -------- | ------ |\n\n---\n\n## Issues ouvertes ({count} total)\n\n| # | Auteur | Sujet | Priorité |\n| - | ------ | ----- | -------- |\n\n---\n\n## Résumé exécutif\n\n- **Point 1**: ...\n- **Point 2**: ...\n```\n\n## Output Template (EN)\n\nSame structure but with English headers:\n- \"Recent Releases\", \"Open PRs\", \"Our PRs\", \"External — Reviewable\", \"External — Problematic\", \"Open Issues\", \"Executive Summary\"\n- Action labels: \"To review\", \"Rebase requested\", \"Split requested\", \"Trim requested\", \"CI broken\", \"Waiting on author\", \"Feature request\", \"Quick fix\", \"Covered by PR\"\n\n## Notes\n\n- Always use `gh` CLI (not GitHub API directly, except for collaborators list)\n- Derive repo owner\u002Fname from `gh repo view`, don't hardcode\n- Keep tables compact — truncate long titles if needed (max ~60 chars)\n- Cross-reference overlapping PRs\u002Fissues whenever possible\n- `author` in gh JSON is an object — always use `.author.login`\n","# Repo Recap\n\nGenerate a structured recap of the repository state: open PRs, open issues, recent releases, and executive summary. Output is formatted as Markdown with clickable GitHub links, ready to share.\n\n## Language\n\n- Check the argument passed to this skill\n- If `en` or `english` → produce the recap in English\n- If `fr`, `french`, or no argument → produce the recap in French (default)\n\n## Preconditions\n\nBefore gathering data, verify:\n\n```bash\n# Must be inside a git repo\ngit rev-parse --is-inside-work-tree\n\n# Must have gh CLI authenticated\ngh auth status\n```\n\nIf either fails, stop and tell the user what's missing.\n\n## Steps\n\n### 1. Gather Data\n\nRun these commands in parallel via `gh` CLI:\n\n```bash\n# Repo identity (for links)\ngh repo view --json nameWithOwner -q .nameWithOwner\n\n# Open PRs with metadata\ngh pr list --state open --limit 50 --json number,title,author,createdAt,changedFiles,additions,deletions,reviewDecision,isDraft\n\n# Open issues with metadata\ngh issue list --state open --limit 50 --json number,title,author,createdAt,labels,assignees\n\n# Recent releases (for version history)\ngh release list --limit 5\n\n# Recently merged PRs (for contributor activity)\ngh pr list --state merged --limit 10 --json number,title,author,mergedAt\n```\n\nNote: `author` in JSON results is an object `{login: \"...\"}` — always extract `.author.login` when processing.\n\n### 2. Determine Maintainers\n\nTo distinguish \"our PRs\" from external contributions:\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fcollaborators --jq '.[].login'\n```\n\nIf this fails (permissions), fallback: authors with write\u002Fadmin access are those who merged PRs recently. When in doubt, ask the user.\n\n### 3. Analyze and Categorize\n\n#### PRs — Categorize into 3 groups:\n\n**Our PRs** (author is a repo collaborator):\n- List with PR number (linked), title, size (+additions, files count), status\n\n**External — Reviewable** (manageable size, no major blockers):\n- Additions ≤ 1000 AND files ≤ 10\n- No merge conflicts, CI not failing\n- Include: PR link, author, title, size, review status, recommended action\n\n**External — Problematic** (any of: too large, CI failing, overlapping, merge conflict):\n- Additions > 1000 OR files > 10\n- OR CI failing (reviewDecision = \"CHANGES_REQUESTED\" or checks failing)\n- OR touches same files as another open PR (= overlap)\n- Include: PR link, author, title, size, specific problem, action taken\u002Fneeded\n\n**Size labels** (use in \"Taille\" column for quick visual triage):\n\n| Label | Additions |\n| ----- | --------- |\n| XS | \u003C 50 |\n| S | 50-200 |\n| M | 200-500 |\n| L | 500-1000 |\n| XL | > 1000 |\n\nFormat: `+{additions}, {files} files ({label})` — e.g., `+245, 2 files (S)`\n\n#### Detect overlaps:\nTwo PRs overlap if they modify the same files. Use `changedFiles` from the JSON data. If >50% file overlap between 2 PRs, flag both as overlapping and cross-reference them.\n\n#### Flag clusters:\nIf one author has 3+ open PRs, note it as a \"cluster\" with suggested review order (smallest first, or by dependency chain).\n\n#### Issues — Categorize by status:\n- **In progress**: has an associated open PR (match by PR body containing `fixes #N`, `closes #N`, or same topic)\n- **Quick fix**: small scope, actionable (bug reports, small enhancements)\n- **Feature request**: larger scope, needs design discussion\n- **Covered by PR**: an existing PR addresses this issue (link it)\n\n### 4. Derive Recent Releases\n\nFrom `gh release list` output, extract version, date, and name. List the 5 most recent.\n\nIf no releases found, check merged PRs for release-please pattern (title matching `chore(*): release *`) as fallback.\n\n### 5. Executive Summary\n\nProduce 5-6 bullet points:\n- Total open PRs and issues count\n- Active contributors (who has the most PRs\u002Fissues)\n- Main risks (oversized PRs, CI failures, merge conflicts)\n- Quick wins (small PRs ready to merge — XS\u002FS size, no blockers)\n- Bug fixes needed (hook bugs, regressions)\n- Our own PRs status\n\n### 6. Format Output\n\nStructure the full recap as Markdown with:\n- `# {Repo Name} — Récap au {date}` as title (FR) or `# {Repo Name} — Recap {date}` (EN)\n- Sections separated by `---`\n- All PR\u002Fissue numbers as clickable links: `[#123](https:\u002F\u002Fgithub.com\u002F{owner}\u002F{repo}\u002Fpull\u002F123)` for PRs, `...\u002Fissues\u002F123` for issues\n- Tables with Markdown pipe syntax for all listings\n- Bold for emphasis on actions and risks\n- Cross-references between related PRs and issues (e.g., \"Covered by [#131](link)\")\n\n**Empty data handling**:\n- 0 open PRs → display \"Aucune PR ouverte.\" (FR) or \"No open PRs.\" (EN) instead of empty table\n- 0 open issues → display \"Aucune issue ouverte.\" (FR) or \"No open issues.\" (EN)\n- 0 releases → display \"Aucune release récente.\" (FR) or \"No recent releases.\" (EN)\n\n### 7. Copy to Clipboard\n\nAfter displaying the recap, automatically copy it to clipboard:\n\n```bash\n# Cross-platform clipboard\nclip() {\n  if command -v pbcopy &>\u002Fdev\u002Fnull; then pbcopy\n  elif command -v xclip &>\u002Fdev\u002Fnull; then xclip -selection clipboard\n  elif command -v wl-copy &>\u002Fdev\u002Fnull; then wl-copy\n  else cat\n  fi\n}\n\ncat \u003C\u003C 'EOF' | clip\n{formatted recap content}\nEOF\n```\n\nConfirm with: \"Copié dans le presse-papier.\" (FR) or \"Copied to clipboard.\" (EN)\n\n## Output Template (FR)\n\n```markdown\n# {Repo Name} — Récap au {date}\n\n## Releases récentes\n\n| Version | Date | Highlights |\n| ------- | ---- | ---------- |\n| ...     | ...  | ...        |\n\n---\n\n## PRs ouvertes ({count} total)\n\n### Nos PRs\n\n| PR | Titre | Taille | Status |\n| -- | ----- | ------ | ------ |\n\n### Contributeurs externes — Reviewables\n\n| PR | Auteur | Titre | Taille | Status | Action |\n| -- | ------ | ----- | ------ | ------ | ------ |\n\n### Contributeurs externes — Problématiques\n\n| PR | Auteur | Titre | Taille | Problème | Action |\n| -- | ------ | ----- | ------ | -------- | ------ |\n\n---\n\n## Issues ouvertes ({count} total)\n\n| # | Auteur | Sujet | Priorité |\n| - | ------ | ----- | -------- |\n\n---\n\n## Résumé exécutif\n\n- **Point 1**: ...\n- **Point 2**: ...\n```\n\n## Output Template (EN)\n\nSame structure but with English headers:\n- \"Recent Releases\", \"Open PRs\", \"Our PRs\", \"External — Reviewable\", \"External — Problematic\", \"Open Issues\", \"Executive Summary\"\n- Action labels: \"To review\", \"Rebase requested\", \"Split requested\", \"Trim requested\", \"CI broken\", \"Waiting on author\", \"Feature request\", \"Quick fix\", \"Covered by PR\"\n\n## Notes\n\n- Always use `gh` CLI (not GitHub API directly, except for collaborators list)\n- Derive repo owner\u002Fname from `gh repo view`, don't hardcode\n- Keep tables compact — truncate long titles if needed (max ~60 chars)\n- Cross-reference overlapping PRs\u002Fissues whenever possible\n- `author` in gh JSON is an object — always use `.author.login`\n",{"description":7,"allowed-tools":23},"Bash Read Grep","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Frepo-recap","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Sansar35\u002Fclaude-agent --skill repo-recap",{"tool":36,"command":37},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill repo-recap",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill repo-recap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Frepo-recap\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},".skill-source.json","REFERENCE","参考文档",337,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Frepo-recap\u002F.skill-source.json",[51,58,65,72,79,87],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]