[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MCSJV453XY63TCW1AV9H7":3,"skill-same:01M71MCSJV453XY63TCW1AV9H7":77},{"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":26,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M71MCSJV453XY63TCW1AV9H7","github",null,"GitHub patterns using gh CLI for pull requests, stacked PRs, code review, branching strategies, and repository automation. Use when working with GitHub PRs, merging strategies, or repository management tasks.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_callstackincubator_github\u002Fskill.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[5,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"squash","when","prs","gh-cli","for","requests","with","strategies","use","gh","code review","pull","code","tasks","pr","pull requests","automation","cli","review","2026-11-10 10:56:23",false,"---\nname: github\ndescription: GitHub patterns using gh CLI for pull requests, stacked PRs, code review, branching strategies, and repository automation. Use when working with GitHub PRs, merging strategies, or repository management tasks.\nlicense: MIT\nmetadata:\n  author: Callstack\n  tags: github, gh-cli, pull-request, stacked-pr, squash, rebase\n---\n\n# GitHub Patterns\n\n## Tools\n\nUse `gh` CLI for all GitHub operations. Prefer CLI over GitHub MCP servers for lower context usage.\n\n## Quick Commands\n\n```bash\n# Create a PR from the current branch\ngh pr create --title \"feat: add feature\" --body \"Description\"\n\n# Squash-merge a PR\ngh pr merge \u003CPR_NUMBER> --squash --title \"feat: add feature (#\u003CPR_NUMBER>)\"\n\n# View PR status and checks\ngh pr status\ngh pr checks \u003CPR_NUMBER>\n```\n\n## Stacked PR Workflow Summary\n\nWhen merging a chain of stacked PRs (each targeting the previous branch):\n\n1. **Merge the first PR** into main via squash merge\n2. **For each subsequent PR**: rebase onto main, update base to main, then squash merge\n3. **On conflicts**: stop and ask the user to resolve manually\n\n```bash\n# Rebase next PR's branch onto main, excluding already-merged commits\ngit rebase --onto origin\u002Fmain \u003Cold-base-branch> \u003Cnext-branch>\ngit push --force-with-lease origin \u003Cnext-branch>\ngh pr edit \u003CN> --base main\ngh pr merge \u003CN> --squash --title \"\u003CPR title> (#N)\"\n```\n\nSee [stacked_pr_workflow.md][stacked-pr-workflow] for full step-by-step details.\n\n## Quick Reference\n\n| File | Description |\n| --- | --- |\n| [stacked_pr_workflow.md][stacked-pr-workflow] | Merge stacked PRs into main as individual squash commits |\n\n## Problem -> Skill Mapping\n\n| Problem | Start With |\n| --- | --- |\n| Merge stacked PRs cleanly | [stacked_pr_workflow.md][stacked-pr-workflow] |\n\n[stacked-pr-workflow]: references\u002Fstacked_pr_workflow.md\n","# GitHub Patterns\n\n## Tools\n\nUse `gh` CLI for all GitHub operations. Prefer CLI over GitHub MCP servers for lower context usage.\n\n## Quick Commands\n\n```bash\n# Create a PR from the current branch\ngh pr create --title \"feat: add feature\" --body \"Description\"\n\n# Squash-merge a PR\ngh pr merge \u003CPR_NUMBER> --squash --title \"feat: add feature (#\u003CPR_NUMBER>)\"\n\n# View PR status and checks\ngh pr status\ngh pr checks \u003CPR_NUMBER>\n```\n\n## Stacked PR Workflow Summary\n\nWhen merging a chain of stacked PRs (each targeting the previous branch):\n\n1. **Merge the first PR** into main via squash merge\n2. **For each subsequent PR**: rebase onto main, update base to main, then squash merge\n3. **On conflicts**: stop and ask the user to resolve manually\n\n```bash\n# Rebase next PR's branch onto main, excluding already-merged commits\ngit rebase --onto origin\u002Fmain \u003Cold-base-branch> \u003Cnext-branch>\ngit push --force-with-lease origin \u003Cnext-branch>\ngh pr edit \u003CN> --base main\ngh pr merge \u003CN> --squash --title \"\u003CPR title> (#N)\"\n```\n\nSee [stacked_pr_workflow.md][stacked-pr-workflow] for full step-by-step details.\n\n## Quick Reference\n\n| File | Description |\n| --- | --- |\n| [stacked_pr_workflow.md][stacked-pr-workflow] | Merge stacked PRs into main as individual squash commits |\n\n## Problem -> Skill Mapping\n\n| Problem | Start With |\n| --- | --- |\n| Merge stacked PRs cleanly | [stacked_pr_workflow.md][stacked-pr-workflow] |\n\n[stacked-pr-workflow]: references\u002Fstacked_pr_workflow.md\n",{"name":5,"license":15,"metadata":51,"description":7},{"tags":52,"author":53},"github, gh-cli, pull-request, stacked-pr, squash, rebase","Callstack","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fofficial_callstackincubator_github",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill github",{"tool":69,"command":70},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill github",{"tool":72,"command":73},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill github","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_callstackincubator_github\u002Fskill.md",true,[],[78,108,129,150,169,192],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":87,"publishedAt":107},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[88,89,90,91,92,93,94,95,96,97,98,99,100,101,28,102,103,104,105,106],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":107},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[114],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[88,116,117,92,118,119,120,121,101,122,28,40,102,123,124,125,126,127,128,31],"react native","native","vercel react native skills","react native skills","modules","performance","apps","mobile","expo","list","mobile performance","platform","animations",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":107},"01M71P8QK4JF5BYRGYDDGPZQG9","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\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[135],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[88,137,138,92,139,121,140,28,39,40,102,141,142,143,144,145,146,147,148,149],"react best practices","vercel react best practices","best practices","writing","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":107},"01M71P8HVEA70K5N6ZVJCG2ED3","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\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[156],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[158,92,159,146,160,161,162,163,149,164,165,35,28,166,40,102,167,168,103,88],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":107},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[179,180,181,182,139,183,184,185,31,147,121,186,187,140,188,35,189,190,191,28],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":46},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[198],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[200,201,202,203,204,98,205,163,206,101,207,208,28,88,209,210,211,212,213,214],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue"]