[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79NNZXQJXMXQSRGKVVSTSMH":3,"skill-same:01M79NNZXQJXMXQSRGKVVSTSMH":74},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79NNZXQJXMXQSRGKVVSTSMH","gh-address-comments",null,"Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes. Use the GitHub app for PR metadata and flat comment reads, and use the bundled GraphQL script via `gh` whenever thread-level state, resolution status, or inline review context matters.","MeghVyas3132\u002FClaude-Code-Skills","MeghVyas3132","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F213562095?v=4","01M79MBRQ3EM1GSWXK3QVWPYK6","Megh Vyas","01M79MBRQRZNC3QS0FS1KC6Z09",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fgithub\u002Fgh-address-comments\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fgithub\u002Fgh-address-comments\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gh-address-comments\ndescription: Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes. Use the GitHub app for PR metadata and flat comment reads, and use the bundled GraphQL script via `gh` whenever thread-level state, resolution status, or inline review context matters.\n---\n\n# GitHub PR Comment Handler\n\nUse this skill when the user wants to work through requested changes on a GitHub pull request. Use the GitHub app from this plugin for PR metadata and patch context, but treat thread-aware review data as a `gh api graphql` problem because the connector comment surface is flat and does not preserve full review-thread state.\n\nRun all `gh` commands with elevated network access. If CLI auth is required, confirm `gh auth status` first and ask the user to authenticate with `gh auth login` if it fails.\n\n## Workflow\n\n1. Resolve the PR.\n   - If the user provides a repository and PR number or URL, use that directly.\n   - If the request is about the current branch PR, use local git context plus `gh auth status` and `gh pr view --json number,url` to resolve it.\n2. Inspect review context with thread-aware reads.\n   - Use the GitHub app from this plugin to fetch PR metadata and patch context when the repo and PR are known.\n   - Use the bundled `scripts\u002Ffetch_comments.py` workflow whenever the task depends on unresolved review threads, inline review locations, or resolution state. That script fetches `reviewThreads`, `isResolved`, `isOutdated`, and file and line anchors that the connector comment surface does not preserve.\n   - Use connector-only comment reads only for lightweight top-level PR comment summaries.\n3. Cluster actionable review threads.\n   - Group comments by file or behavior area.\n   - Separate actionable change requests from informational comments, approvals, already-resolved threads, and duplicates.\n4. Confirm scope before editing.\n   - Present numbered actionable threads with a one-line summary of the required change.\n   - If the user did not ask to fix everything, ask which threads to address.\n   - If the user asks to fix everything, interpret that as all unresolved actionable threads and call out anything ambiguous.\n5. Implement the selected fixes locally.\n   - Keep each code change traceable back to the thread or feedback cluster it addresses.\n   - If a comment calls for explanation rather than code, draft the response rather than forcing a code change.\n6. Summarize the result.\n   - List which threads were addressed, which were intentionally left open, and what tests or checks support the change.\n\n## Write Safety\n\n- Do not reply on GitHub, resolve review threads, or submit a review unless the user explicitly asks for that write action.\n- If review comments conflict with each other or would cause a behavioral regression, surface the tradeoff before making changes.\n- If a comment is ambiguous, ask for clarification or draft a proposed response instead of guessing.\n- Do not treat flat PR comments from the connector as a complete representation of review-thread state.\n- If `gh` hits auth or rate-limit issues mid-run, ask the user to re-authenticate and retry.\n\n## Fallback\n\nIf neither the connector nor `gh` can resolve the PR cleanly, tell the user whether the blocker is missing repository scope, missing PR context, or CLI authentication, then ask for the missing repo or PR identifier or for a refreshed `gh` login.\n","# GitHub PR Comment Handler\n\nUse this skill when the user wants to work through requested changes on a GitHub pull request. Use the GitHub app from this plugin for PR metadata and patch context, but treat thread-aware review data as a `gh api graphql` problem because the connector comment surface is flat and does not preserve full review-thread state.\n\nRun all `gh` commands with elevated network access. If CLI auth is required, confirm `gh auth status` first and ask the user to authenticate with `gh auth login` if it fails.\n\n## Workflow\n\n1. Resolve the PR.\n   - If the user provides a repository and PR number or URL, use that directly.\n   - If the request is about the current branch PR, use local git context plus `gh auth status` and `gh pr view --json number,url` to resolve it.\n2. Inspect review context with thread-aware reads.\n   - Use the GitHub app from this plugin to fetch PR metadata and patch context when the repo and PR are known.\n   - Use the bundled `scripts\u002Ffetch_comments.py` workflow whenever the task depends on unresolved review threads, inline review locations, or resolution state. That script fetches `reviewThreads`, `isResolved`, `isOutdated`, and file and line anchors that the connector comment surface does not preserve.\n   - Use connector-only comment reads only for lightweight top-level PR comment summaries.\n3. Cluster actionable review threads.\n   - Group comments by file or behavior area.\n   - Separate actionable change requests from informational comments, approvals, already-resolved threads, and duplicates.\n4. Confirm scope before editing.\n   - Present numbered actionable threads with a one-line summary of the required change.\n   - If the user did not ask to fix everything, ask which threads to address.\n   - If the user asks to fix everything, interpret that as all unresolved actionable threads and call out anything ambiguous.\n5. Implement the selected fixes locally.\n   - Keep each code change traceable back to the thread or feedback cluster it addresses.\n   - If a comment calls for explanation rather than code, draft the response rather than forcing a code change.\n6. Summarize the result.\n   - List which threads were addressed, which were intentionally left open, and what tests or checks support the change.\n\n## Write Safety\n\n- Do not reply on GitHub, resolve review threads, or submit a review unless the user explicitly asks for that write action.\n- If review comments conflict with each other or would cause a behavioral regression, surface the tradeoff before making changes.\n- If a comment is ambiguous, ask for clarification or draft a proposed response instead of guessing.\n- Do not treat flat PR comments from the connector as a complete representation of review-thread state.\n- If `gh` hits auth or rate-limit issues mid-run, ask the user to re-authenticate and retry.\n\n## Fallback\n\nIf neither the connector nor `gh` can resolve the PR cleanly, tell the user whether the blocker is missing repository scope, missing PR context, or CLI authentication, then ask for the missing repo or PR identifier or for a refreshed `gh` login.\n",{"name":5,"description":7},"main","12a76cdd6f897f0872b282adeec07c7a07cf6bcc","_other-tools\u002Fcodex\u002Fgithub\u002Fgh-address-comments","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills","https:\u002F\u002Fgithub.com\u002FMeghVyas3132","https:\u002F\u002Fmegh.tech","Entrepreneur \u002F Platform Engineer \u002F DevOps \u002F Backend developer \u002F System Architect \u002F Salesforce admin-dev \u002F AI Engineer \u002F Junior SRE","2026-07-25 05:29:37",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add MeghVyas3132\u002FClaude-Code-Skills --skill gh-address-comments",{"tool":39,"command":40},"bunx","bunx skills add MeghVyas3132\u002FClaude-Code-Skills --skill gh-address-comments",{"tool":42,"command":43},"pnpm","pnpm dlx skills add MeghVyas3132\u002FClaude-Code-Skills --skill gh-address-comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fgithub\u002Fgh-address-comments\u002FSKILL.md",true,[47,53,59,63,68],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",325,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fgithub\u002Fgh-address-comments\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fgithub-small.svg","ASSET","资产文件",853,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fgithub\u002Fgh-address-comments\u002Fassets\u002Fgithub-small.svg",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fgithub.png",1838,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fgithub\u002Fgh-address-comments\u002Fassets\u002Fgithub.png",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",11357,{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Ffetch_comments.py","SCRIPT","脚本",6537,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fgithub\u002Fgh-address-comments\u002Fscripts\u002Ffetch_comments.py",[75,83,91,98,105,112],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":20},"01M79QXVKBA07BMENY2S4C9B0D","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M79QXPTA7529Z7QX9TYC9X8M","skill-audit","Pre-install security scanner for AI agent skills. 7.5% of 14,706 skills are malicious. Audit before you trust.","MIT","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-audit\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M79QWZ2BB5GTX3PCHEEDG3A2","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Freact-best-practices\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M79QWAADBR52R570H6N25F47","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fimpeccable\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M79QTGQJGPXPJDB09WBZHRND","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fcomposition-patterns\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M79QT5TCZBBKP5ECWE0QD9PT","bumblebee","Run Bumblebee supply-chain inventory and exposure scans on macOS\u002FLinux to detect compromised packages, extensions, and MCP host configs.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fbumblebee\u002FSKILL.md",[],[]]