[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K13WMAP6GCJ5KSDSWK9WBV":3,"skill-same:01M6K13WMAP6GCJ5KSDSWK9WBV":81},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6K13WMAP6GCJ5KSDSWK9WBV","github",null,"Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.","NagyVikt\u002Fcodex-plugins","NagyVikt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F137165288?v=4","01M6K0SJ3R2DAZRJKJJS10VN87","Viktor Nagy","01M6K0SJ9HXN0GBD91QDQ9WNVV",2,"MIT","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgithub\u002Fskills\u002Fgithub\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"context","summaries","for","more","app","orient","general","issue","use","user","work","repository","pull","help","pull request","pr","workflow","triage","2026-11-10 10:12:30",false,"---\nname: github\ndescription: Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.\n---\n\n# GitHub\n\n## Overview\n\nUse this skill as the umbrella entrypoint for general GitHub work in this plugin. It should decide whether the task stays in repo and PR triage or should be handed off to a more specific review, CI, or publish workflow.\n\nThis plugin is intentionally hybrid:\n\n- Prefer the GitHub app from this plugin for repository, issue, pull request, comment, label, reaction, and PR creation workflows.\n- Use local `git` and `gh` only when the connector does not cover the job well, especially for current-branch PR discovery, branch creation, commit and push, `gh auth status`, and GitHub Actions log inspection.\n- Keep connector state and local checkout context aligned. If the request is about the current branch, resolve the local repo and branch before acting.\n\nOnce the intent is clear, route to the specialist skill immediately and do not keep broad GitHub triage in scope longer than needed.\n\n## Connector-First Responsibilities\n\nHandle these directly in this skill when the request does not need a narrower specialist workflow:\n\n- repository orientation once the repo, PR, issue, or local checkout is identified\n- recent PR or issue triage\n- PR metadata summaries\n- PR patch inspection\n- PR comments, labels, and reactions\n- issue lookup and summarization\n- PR creation after a branch is already pushed\n\nPrefer the GitHub app from this plugin for those flows because it provides structured PR, issue, and review-adjacent data without depending on a local checkout. If the repository is not already identifiable from the user request or local git context, ask for the repo instead of pretending there is a repo-search flow that may not exist.\n\n## Routing Rules\n\n1. Resolve the operating context first:\n   - If the user provides a repository, PR number, issue number, or URL, use that.\n   - If the request is about \"this branch\" or \"the current PR\", resolve local git context and use `gh` only as needed to discover the branch PR.\n   - If the repository is still ambiguous after local inspection, ask for the repo identifier.\n2. Classify the request before taking action:\n   - `repo or PR triage`: summarize PRs, issues, patches, comments, labels, reactions, or repository state\n   - `review follow-up`: unresolved review threads, requested changes, or inline review feedback\n   - `CI debugging`: failing checks, Actions logs, or CI root-cause analysis\n   - `publish changes`: create or switch branches, stage changes, commit, push, and open a draft PR\n   - `post-plan auto publish`: implementation is complete, checks passed, and changes should be committed and pushed automatically\n3. Route to the specialist skill as soon as the category is clear:\n   - Review comments and requested changes: `..\u002Fgh-address-comments\u002FSKILL.md`\n   - Failing GitHub Actions checks: `..\u002Fgh-fix-ci\u002FSKILL.md`\n   - Commit, push, and open PR: `..\u002Fyeet\u002FSKILL.md`\n   - Auto commit and push after verified implementation: `..\u002Fauto-publish-after-plan\u002FSKILL.md`\n4. Keep the hybrid model consistent after routing:\n   - connector first for PR and issue data\n   - local `git` and `gh` only for the specific gaps the connector does not cover\n\n## Default Workflow\n\n1. Resolve repository and item scope.\n2. Gather structured PR or issue context through the GitHub app from this plugin.\n3. Decide whether the task stays in connector-backed triage or needs a specialist skill.\n4. Route immediately when the work becomes review follow-up, CI debugging, or publish workflow.\n   - If the user asks for automatic post-plan commit\u002Fpush behavior, route to `auto-publish-after-plan`.\n5. End with a clear summary of what was inspected, what changed, and what remains.\n\n## Output Expectations\n\n- For triage requests, return a concise summary of the repository, PR, or issue state and the next likely action.\n- For mixed requests, tell the user which specialist path you are taking and why.\n- For connector-backed write actions, restate the exact PR, issue, label, or reaction target before applying the change.\n- Never imply that GitHub Actions logs are available through the connector alone. That remains a `gh` workflow.\n\n## Examples\n\n- \"Use GitHub to summarize the open PRs in this repo and tell me what needs attention.\"\n- \"Help with this PR.\"\n- \"Review the latest comments on PR 482 and tell me what is actionable.\"\n- \"Debug the failing checks on this branch.\"\n- \"Commit these changes, push them, and open a draft PR.\"\n- \"Plan is implemented and verified; auto-commit and push this branch.\"\n","# GitHub\n\n## Overview\n\nUse this skill as the umbrella entrypoint for general GitHub work in this plugin. It should decide whether the task stays in repo and PR triage or should be handed off to a more specific review, CI, or publish workflow.\n\nThis plugin is intentionally hybrid:\n\n- Prefer the GitHub app from this plugin for repository, issue, pull request, comment, label, reaction, and PR creation workflows.\n- Use local `git` and `gh` only when the connector does not cover the job well, especially for current-branch PR discovery, branch creation, commit and push, `gh auth status`, and GitHub Actions log inspection.\n- Keep connector state and local checkout context aligned. If the request is about the current branch, resolve the local repo and branch before acting.\n\nOnce the intent is clear, route to the specialist skill immediately and do not keep broad GitHub triage in scope longer than needed.\n\n## Connector-First Responsibilities\n\nHandle these directly in this skill when the request does not need a narrower specialist workflow:\n\n- repository orientation once the repo, PR, issue, or local checkout is identified\n- recent PR or issue triage\n- PR metadata summaries\n- PR patch inspection\n- PR comments, labels, and reactions\n- issue lookup and summarization\n- PR creation after a branch is already pushed\n\nPrefer the GitHub app from this plugin for those flows because it provides structured PR, issue, and review-adjacent data without depending on a local checkout. If the repository is not already identifiable from the user request or local git context, ask for the repo instead of pretending there is a repo-search flow that may not exist.\n\n## Routing Rules\n\n1. Resolve the operating context first:\n   - If the user provides a repository, PR number, issue number, or URL, use that.\n   - If the request is about \"this branch\" or \"the current PR\", resolve local git context and use `gh` only as needed to discover the branch PR.\n   - If the repository is still ambiguous after local inspection, ask for the repo identifier.\n2. Classify the request before taking action:\n   - `repo or PR triage`: summarize PRs, issues, patches, comments, labels, reactions, or repository state\n   - `review follow-up`: unresolved review threads, requested changes, or inline review feedback\n   - `CI debugging`: failing checks, Actions logs, or CI root-cause analysis\n   - `publish changes`: create or switch branches, stage changes, commit, push, and open a draft PR\n   - `post-plan auto publish`: implementation is complete, checks passed, and changes should be committed and pushed automatically\n3. Route to the specialist skill as soon as the category is clear:\n   - Review comments and requested changes: `..\u002Fgh-address-comments\u002FSKILL.md`\n   - Failing GitHub Actions checks: `..\u002Fgh-fix-ci\u002FSKILL.md`\n   - Commit, push, and open PR: `..\u002Fyeet\u002FSKILL.md`\n   - Auto commit and push after verified implementation: `..\u002Fauto-publish-after-plan\u002FSKILL.md`\n4. Keep the hybrid model consistent after routing:\n   - connector first for PR and issue data\n   - local `git` and `gh` only for the specific gaps the connector does not cover\n\n## Default Workflow\n\n1. Resolve repository and item scope.\n2. Gather structured PR or issue context through the GitHub app from this plugin.\n3. Decide whether the task stays in connector-backed triage or needs a specialist skill.\n4. Route immediately when the work becomes review follow-up, CI debugging, or publish workflow.\n   - If the user asks for automatic post-plan commit\u002Fpush behavior, route to `auto-publish-after-plan`.\n5. End with a clear summary of what was inspected, what changed, and what remains.\n\n## Output Expectations\n\n- For triage requests, return a concise summary of the repository, PR, or issue state and the next likely action.\n- For mixed requests, tell the user which specialist path you are taking and why.\n- For connector-backed write actions, restate the exact PR, issue, label, or reaction target before applying the change.\n- Never imply that GitHub Actions logs are available through the connector alone. That remains a `gh` workflow.\n\n## Examples\n\n- \"Use GitHub to summarize the open PRs in this repo and tell me what needs attention.\"\n- \"Help with this PR.\"\n- \"Review the latest comments on PR 482 and tell me what is actionable.\"\n- \"Debug the failing checks on this branch.\"\n- \"Commit these changes, push them, and open a draft PR.\"\n- \"Plan is implemented and verified; auto-commit and push this branch.\"\n",{"name":5,"description":7},"main","9a4409c8751439c3aeeea2bc3940ba05dc3cd3b5","plugins\u002Fgithub\u002Fskills\u002Fgithub",0,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FNagyVikt","https:\u002F\u002Fwebu.hu\u002F","Codex is a tool they said...\r\n\r\nCreator of GitGuardex, CueCards. Tech stack: Next.js · TypeScript · Rust · Linux. ","2026-03-30 02:19:53",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add NagyVikt\u002Fcodex-plugins --skill github",{"tool":57,"command":58},"bunx","bunx skills add NagyVikt\u002Fcodex-plugins --skill github",{"tool":60,"command":61},"pnpm","pnpm dlx skills add NagyVikt\u002Fcodex-plugins --skill github","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgithub\u002Fskills\u002Fgithub\u002FSKILL.md",true,[65,71,77],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",318,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgithub\u002Fskills\u002Fgithub\u002Fagents\u002Fopenai.yaml",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"assets\u002Fgithub-small.svg","ASSET","资产文件",853,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgithub\u002Fskills\u002Fgithub\u002Fassets\u002Fgithub-small.svg",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Fgithub.png",1838,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgithub\u002Fskills\u002Fgithub\u002Fassets\u002Fgithub.png",[82,123,156,180,209,231],{"skillNo":83,"name":35,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":103,"publishedAt":37},"01M6K1ZEN8P9R2S6NPNJNJ8JVH","Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[87,92,95,100],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000038","人力资源",[35,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122],"workflows","create","run","streaming","logs","start","why","loop","wait for","branch","auto","log","conversation","human","lib","condition","rendering","retries","sleep",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":139,"publishedAt":37},"01M6K1Z71NWFSPHK2VJJ73MVSY","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[129,132,133,136],{"categoryNo":130,"categoryName":131,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":134,"categoryName":135,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":137,"categoryName":138,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000033","数据分析师",[125,140,107,141,142,143,113,144,145,146,147,148,149,23,150,151,152,153,154,155],"auth","routing middleware","api","projects","user story","full stack","jest","local","project","end","false","unit","error","middleware","loading","unit test",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":37},"01M6K1YPRYJS3BQEDP8HKBHPEJ","vercel-storage","Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[162],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[164,165,166,167,106,168,169,114,170,171,172,173,174,175,23,118,176,177,178,179],"storage","vercel storage","vercel","config","supabase","migrate","router","clerk","expert","prisma","connection pooling","neon","turso","upstash","URL","auth0",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":193,"publishedAt":37},"01M6K1YFEP0GPPGMQ3D0FPTS27","vercel-services","Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[186,189,190],{"categoryNo":187,"categoryName":188,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":191,"categoryName":192,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000011","运维与部署",[194,195,166,196,197,198,199,200,201,202,203,42,204,205,148,206,23,207,152,208],"vercel services","services","frontend","docker compose","SET","configure","monorepo","go api","fastapi","up","aws lambda","go backend","get","apps","python backend",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":37},"01M6K1Y8S3CRD43DPKX0PK1MTT","vercel-sandbox","Vercel Sandbox guidance — ephemeral Firecracker microVMs for running untrusted code safely. Supports AI agents, code generation, and experimentation. Use when executing user-generated or AI-generated code in isolation.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[216,217,166,218,219,105,106,220,221,222,223,224,225,226,227,228,154,229,211,230],"sandbox","vercel sandbox","safe","ai agents","code","ai sdk","Code Generation","playground","generated","spawn","install","runner","io","child","student",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":238,"publishedAt":37},"01M6K1Y1J8S7AN97H75SHBGF7J","vercel-queues","Vercel Queues guidance (public beta) — durable event streaming with topics, consumer groups, retries, and delayed delivery. $0.60\u002F1M ops. Powers Workflow DevKit. Use when building async processing, fan-out patterns, or event-driven architectures.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-queues\u002FSKILL.md",[237],{"categoryNo":93,"categoryName":94,"taxonomyType":90,"taxonomyTypeDesc":91},[239,166,35,104,107,240,198,142,199,203,241,242,243,244,23,118,245,121,154,246],"vercel queues","beta","message","delivery","across","worker","processing","at"]