[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M755AX5DF1W73YZABYGFVN8W":3,"skill-same:01M755AX5DF1W73YZABYGFVN8W":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M755AX5DF1W73YZABYGFVN8W","suggest-reviewers",null,"Suggest GitHub reviewers for the current branch's Pull Request by ranking the people who actually own and recently touched the changed files (git history + CODEOWNERS). Use when the user asks who should review this PR\u002Fbranch or wants reviewer suggestions. Also invoked as the final step of the github-pr skill.","javierponferradalopez\u002Fskills","javierponferradalopez","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14855436?v=4","01M7558SVYVYNG1XCWZEFPK4E6","Javier Ponferrada López","01M7558SWMWTGK5WCJSVFNZ17Y",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fsuggest-reviewers\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: suggest-reviewers\ndescription: Suggest GitHub reviewers for the current branch's Pull Request by ranking the people who actually own and recently touched the changed files (git history + CODEOWNERS). Use when the user asks who should review this PR\u002Fbranch or wants reviewer suggestions. Also invoked as the final step of the github-pr skill.\n---\n\n# Suggest Reviewers\n\nAct as a senior maintainer who knows the codebase's social graph. Given the current branch's diff, produce a ranked, justified shortlist of GitHub users to request review from — grounded in who recently authored the changed files and who owns them via CODEOWNERS.\n\n**Core principle — keep the heavy history out of context.** The `git log`\u002F`git blame` over every changed file can be megabytes. Never read that raw. The bundled script aggregates it in the shell and returns only a compact top-N table (~10 rows). You reason over that table, not over commit history.\n\n## Procedure\n\n1. **Run the ranking script** (it resolves base branch, merge-base, changed files, recency-weighted contributor scores, and email→GitHub-login mapping — all in the shell). The script lives next to this file, in `scripts\u002F` — run it by its path relative to this skill's directory:\n\n   ```bash\n   scripts\u002Frank-contributors.sh --top 10\n   ```\n\n   Pass `--base \u003Cref>` only if the user names a non-default base; `--months`\u002F`--recent-days`\u002F`--top` are tunable but the defaults (12mo window, 90-day recency boost, top 10) are good. The script operates on the repo via `git`, so it works regardless of the directory it's invoked from.\n   - If it exits non-zero, surface the exact error (not a git repo, no merge-base → suggest `git fetch origin`, no history) and stop. Don't fabricate names.\n\n2. **Read CODEOWNERS if present** (`.github\u002FCODEOWNERS`, `CODEOWNERS`, or `docs\u002FCODEOWNERS`). These files are small — reading them into context is fine and expected. Match each changed file (listed in the script's `# changed_files_list:` block) against the ownership patterns and collect the owning `@user`\u002F`@org\u002Fteam` handles. If no CODEOWNERS file exists, skip this silently.\n\n3. **Merge and clean the candidate set:**\n   - **Dedupe linked rows by GitHub login** — the same person may appear under multiple commit emails (e.g. work + personal). Sum their scores into one row. **Do NOT merge unresolved rows together**: every row whose login is `-` is a *distinct* person; dedupe those by name\u002Femail, never by the shared `-` placeholder.\n   - **Exclude the PR author \u002F current user**: `gh api user -q .login`. Never suggest the author as their own reviewer.\n   - **Drop bots only**: skip logins ending in `[bot]`.\n   - **Keep contributors with no linked GitHub account** — they rank by the exact same score as everyone else. A `-` login means GitHub couldn't map their commit email to an account, not that their review is worth less. List them by name `\u003Cemail>` (you cannot `@`-mention them) with a short `(no linked GitHub account — ping manually)` note so the user knows to reach them outside the reviewer field.\n   - **CODEOWNERS owners always make the shortlist**, even if their commit score is low — ownership is an explicit signal. Flag them as owners.\n\n4. **Present the checklist** in the conversation. One line per candidate, ranked (owners and high-score contributors first), each with a one-phrase justification grounded in the data:\n\n   ```\n   Suggested reviewers for this PR (base: \u003Cbase>, \u003CN> files changed):\n\n   - [ ] @ana — CODEOWNER of `commons\u002Fpermissions\u002F**` · 22 recent commits across 5 changed files\n   - [ ] @luis — top contributor: 31 commits, 4\u002F17 changed files\n   - [ ] @marta — recently active in `apps\u002Fpanel\u002F**` (10 commits, last 90 days)\n   - [ ] Diego Ruiz \u003Cdiego@example.com> — top contributor: 18 commits, 6\u002F17 changed files · no linked GitHub account, ping manually\n   ```\n\n   Justifications come from the script columns (score \u002F commits \u002F recent \u002F files) and CODEOWNERS matches — never invented. Contributors without a linked GitHub account appear in the same ranking by score; show them by name `\u003Cemail>` instead of an `@handle`.\n\n## Modes\n\n- **Standalone** (user invoked `\u002Fsuggest-reviewers` directly): output the checklist in the conversation and **stop**. No writes, no `gh pr edit`. The user adds whoever they want themselves.\n- **Called by `github-pr`**: same ranking, but after the user marks their picks the calling skill assigns them to the existing PR with `gh pr edit \u003Cpr> --add-reviewer \u003Chandle,handle>`. Only assign the handles the user explicitly checked. Contributors with no linked GitHub account can't be added this way — if the user picks one, skip the `--add-reviewer` call for them and tell the user to ping that person manually (they have no handle to assign).\n\n## Output\n\nA ranked markdown checklist of GitHub `@handles` with data-backed justifications. Nothing is written to disk or to GitHub in standalone mode.\n\n## Anti-patterns\n\n- ❌ Reading raw `git log`\u002F`git blame` into context instead of using the script's aggregated table — defeats the entire design.\n- ❌ Listing the same person twice because they commit under two emails — dedupe by login.\n- ❌ Dropping a strong contributor just because their commit email isn't linked to a GitHub account — they rank by the same score; list them by name `\u003Cemail>` with a \"ping manually\" note.\n- ❌ Collapsing several unlinked contributors into one row because they all show login `-` — they're different people; dedupe by name\u002Femail.\n- ❌ Suggesting the PR author as a reviewer of their own PR.\n- ❌ Inventing a justification (\"expert in this area\") not backed by the script columns or CODEOWNERS.\n- ❌ Running `gh pr edit --add-reviewer` in standalone mode, or assigning anyone the user didn't explicitly pick.\n- ❌ Failing when CODEOWNERS is absent — it's optional; fall back to history-only ranking.\n","# Suggest Reviewers\n\nAct as a senior maintainer who knows the codebase's social graph. Given the current branch's diff, produce a ranked, justified shortlist of GitHub users to request review from — grounded in who recently authored the changed files and who owns them via CODEOWNERS.\n\n**Core principle — keep the heavy history out of context.** The `git log`\u002F`git blame` over every changed file can be megabytes. Never read that raw. The bundled script aggregates it in the shell and returns only a compact top-N table (~10 rows). You reason over that table, not over commit history.\n\n## Procedure\n\n1. **Run the ranking script** (it resolves base branch, merge-base, changed files, recency-weighted contributor scores, and email→GitHub-login mapping — all in the shell). The script lives next to this file, in `scripts\u002F` — run it by its path relative to this skill's directory:\n\n   ```bash\n   scripts\u002Frank-contributors.sh --top 10\n   ```\n\n   Pass `--base \u003Cref>` only if the user names a non-default base; `--months`\u002F`--recent-days`\u002F`--top` are tunable but the defaults (12mo window, 90-day recency boost, top 10) are good. The script operates on the repo via `git`, so it works regardless of the directory it's invoked from.\n   - If it exits non-zero, surface the exact error (not a git repo, no merge-base → suggest `git fetch origin`, no history) and stop. Don't fabricate names.\n\n2. **Read CODEOWNERS if present** (`.github\u002FCODEOWNERS`, `CODEOWNERS`, or `docs\u002FCODEOWNERS`). These files are small — reading them into context is fine and expected. Match each changed file (listed in the script's `# changed_files_list:` block) against the ownership patterns and collect the owning `@user`\u002F`@org\u002Fteam` handles. If no CODEOWNERS file exists, skip this silently.\n\n3. **Merge and clean the candidate set:**\n   - **Dedupe linked rows by GitHub login** — the same person may appear under multiple commit emails (e.g. work + personal). Sum their scores into one row. **Do NOT merge unresolved rows together**: every row whose login is `-` is a *distinct* person; dedupe those by name\u002Femail, never by the shared `-` placeholder.\n   - **Exclude the PR author \u002F current user**: `gh api user -q .login`. Never suggest the author as their own reviewer.\n   - **Drop bots only**: skip logins ending in `[bot]`.\n   - **Keep contributors with no linked GitHub account** — they rank by the exact same score as everyone else. A `-` login means GitHub couldn't map their commit email to an account, not that their review is worth less. List them by name `\u003Cemail>` (you cannot `@`-mention them) with a short `(no linked GitHub account — ping manually)` note so the user knows to reach them outside the reviewer field.\n   - **CODEOWNERS owners always make the shortlist**, even if their commit score is low — ownership is an explicit signal. Flag them as owners.\n\n4. **Present the checklist** in the conversation. One line per candidate, ranked (owners and high-score contributors first), each with a one-phrase justification grounded in the data:\n\n   ```\n   Suggested reviewers for this PR (base: \u003Cbase>, \u003CN> files changed):\n\n   - [ ] @ana — CODEOWNER of `commons\u002Fpermissions\u002F**` · 22 recent commits across 5 changed files\n   - [ ] @luis — top contributor: 31 commits, 4\u002F17 changed files\n   - [ ] @marta — recently active in `apps\u002Fpanel\u002F**` (10 commits, last 90 days)\n   - [ ] Diego Ruiz \u003Cdiego@example.com> — top contributor: 18 commits, 6\u002F17 changed files · no linked GitHub account, ping manually\n   ```\n\n   Justifications come from the script columns (score \u002F commits \u002F recent \u002F files) and CODEOWNERS matches — never invented. Contributors without a linked GitHub account appear in the same ranking by score; show them by name `\u003Cemail>` instead of an `@handle`.\n\n## Modes\n\n- **Standalone** (user invoked `\u002Fsuggest-reviewers` directly): output the checklist in the conversation and **stop**. No writes, no `gh pr edit`. The user adds whoever they want themselves.\n- **Called by `github-pr`**: same ranking, but after the user marks their picks the calling skill assigns them to the existing PR with `gh pr edit \u003Cpr> --add-reviewer \u003Chandle,handle>`. Only assign the handles the user explicitly checked. Contributors with no linked GitHub account can't be added this way — if the user picks one, skip the `--add-reviewer` call for them and tell the user to ping that person manually (they have no handle to assign).\n\n## Output\n\nA ranked markdown checklist of GitHub `@handles` with data-backed justifications. Nothing is written to disk or to GitHub in standalone mode.\n\n## Anti-patterns\n\n- ❌ Reading raw `git log`\u002F`git blame` into context instead of using the script's aggregated table — defeats the entire design.\n- ❌ Listing the same person twice because they commit under two emails — dedupe by login.\n- ❌ Dropping a strong contributor just because their commit email isn't linked to a GitHub account — they rank by the same score; list them by name `\u003Cemail>` with a \"ping manually\" note.\n- ❌ Collapsing several unlinked contributors into one row because they all show login `-` — they're different people; dedupe by name\u002Femail.\n- ❌ Suggesting the PR author as a reviewer of their own PR.\n- ❌ Inventing a justification (\"expert in this area\") not backed by the script columns or CODEOWNERS.\n- ❌ Running `gh pr edit --add-reviewer` in standalone mode, or assigning anyone the user didn't explicitly pick.\n- ❌ Failing when CODEOWNERS is absent — it's optional; fall back to history-only ranking.\n",{"name":5,"description":7},"master","04992213ead85fffed063682ca559e646fab6b82","skills\u002Fproductivity\u002Fsuggest-reviewers","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez","Software Engineer ","2026-11-06 16:15:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add javierponferradalopez\u002Fskills --skill suggest-reviewers",{"tool":37,"command":38},"bunx","bunx skills add javierponferradalopez\u002Fskills --skill suggest-reviewers",{"tool":40,"command":41},"pnpm","pnpm dlx skills add javierponferradalopez\u002Fskills --skill suggest-reviewers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fsuggest-reviewers\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"scripts\u002Frank-contributors.sh","SCRIPT","脚本",4695,"https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fsuggest-reviewers\u002Fscripts\u002Frank-contributors.sh",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M755BAHG2G5JGPT5R650ADN8","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M755B8Z8MKT694CB19FEC6NR","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M755B2W1VQBC4MY04PJQR5CT","walkthrough","Build a throwaway HTML reading guide for a set of changes (dirty tree, local commits, or a PR): what it means for users and for the system, then an ordered walk through the code with links that open each file in the IDE. Orients the human; leaves every quality call to them.","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fwalkthrough\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M755B09H61BH3ZR4CPCMEBDB","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fteach\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M755AT748KXW4CKCYJHR7XB4","setup-skills","Sets up an `## Agent skills` block in AGENTS.md\u002FCLAUDE.md and `docs\u002Fagents\u002F` so the engineering skills know this repo's issue tracker (GitHub, GitLab, ClickUp, or local markdown), domain doc layout, and error tracking. Run as a first-time bootstrap for a repo, or if engineering skills appear to be missing context about the issue tracker, domain docs, or error tracker.","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fsetup-skills\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M755ARA11A2DFS0CHCPV1EVF","resolve-conflicts","Resolve conflict markers left by a rebase, merge or cherry-pick, and orchestrate a stacked rebase.","https:\u002F\u002Fgithub.com\u002Fjavierponferradalopez\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fresolve-conflicts\u002FSKILL.md",[],[]]