[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XFW46AF0WP9CDNHC0C5XBM":3,"skill-same:01M6XFW46AF0WP9CDNHC0C5XBM":65},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6XFW46AF0WP9CDNHC0C5XBM","create-branch",null,"Create a git branch following Sentry naming conventions. Use when asked to \"create a branch\", \"new branch\", \"start a branch\", \"make a branch\", \"switch to a new branch\", or when starting new work on the default branch.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fcreate-branch\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"create branch","branch","create","default","new","when","unknown","naming conventions","naming","make","conventions","switch","community","use","work","work on","start","sentry","git","git branch","2026-11-10 10:12:30",false,"---\nname: create-branch\ndescription: Create a git branch following Sentry naming conventions. Use when asked to \"create a branch\", \"new branch\", \"start a branch\", \"make a branch\", \"switch to a new branch\", or when starting new work on the default branch.\nargument-hint: '[optional description of the work]'\nrisk: unknown\nsource: community\n---\n\n# Create Branch\n\nCreate a git branch with the correct type prefix and a descriptive name following Sentry conventions.\n\n## Step 1: Get the Username Prefix\n\nRun `gh api user --jq .login` to get the GitHub username.\n\nIf the command fails (e.g. not authenticated), ask the user for their preferred prefix.\n\n## Step 2: Determine the Branch Description\n\n**If `$ARGUMENTS` is provided**, use it as the description of the work.\n\n**If no arguments**, check for local changes:\n\n```bash\ngit diff\ngit diff --cached\ngit status --short\n```\n\n- **Changes exist**: read the diff content to understand what the work is about and generate a description.\n- **No changes**: ask the user what they are about to work on.\n\n## Step 3: Classify the Type\n\nPick the type from this table based on the description:\n\n| Type      | Use when                                                              |\n| --------- | --------------------------------------------------------------------- |\n| `feat`    | New user-facing functionality                                         |\n| `fix`     | Broken behavior now works                                             |\n| `ref`     | Same behavior, different structure                                    |\n| `chore`   | Deps, config, version bumps, updating existing tooling — no new logic |\n| `perf`    | Same behavior, faster                                                 |\n| `style`   | CSS, formatting, visual-only                                          |\n| `docs`    | Documentation only                                                    |\n| `test`    | Tests only                                                            |\n| `ci`      | CI\u002FCD config                                                          |\n| `build`   | Build system                                                          |\n| `meta`    | Repo metadata changes                                                 |\n| `license` | License changes                                                       |\n\nWhen unsure: `feat` for new things (including new scripts, skills, or tools), `ref` for restructuring existing things, `chore` only when updating\u002Fmaintaining something that already exists.\n\n## Step 4: Generate and Propose\n\nBuild the branch name as `\u003Cusername>\u002F\u003Ctype>\u002F\u003Cshort-description>`.\n\nRules for `\u003Cshort-description>`:\n\n- Kebab-case, lowercase\n- 3 to 6 words, concise but clear\n- Describe the change, not file names\n- Only use ASCII letters, digits, and hyphens — no spaces, dots, colons, tildes, or other git-forbidden characters\n\nPresent it to the user and ask if they want to use it, modify it, or change the type.\n\n### Examples\n\n| Work description                           | Branch name                                 |\n| ------------------------------------------ | ------------------------------------------- |\n| Dropdown menu not closing on outside click | `priscila\u002Ffix\u002Fdropdown-not-closing-on-blur` |\n| Adding search to conversations page        | `priscila\u002Ffeat\u002Fadd-search-to-conversations` |\n| Restructuring drawer components            | `priscila\u002Fref\u002Fsimplify-drawer-components`   |\n| Updating test fixtures                     | `priscila\u002Fchore\u002Fupdate-test-fixtures`       |\n| Bumping @sentry\u002Freact to latest version    | `priscila\u002Fchore\u002Fbump-sentry-react`          |\n| Adding a new agent skill                   | `priscila\u002Ffeat\u002Fadd-create-branch-skill`     |\n\n## Step 5: Create the Branch\n\nOnce confirmed, detect the current and default branch:\n\n```bash\ngit branch --show-current\ngit remote | grep -qx origin && echo origin || git remote | head -1\ngit symbolic-ref refs\u002Fremotes\u002F\u003Cremote>\u002FHEAD 2>\u002Fdev\u002Fnull | sed 's|refs\u002Fremotes\u002F\u003Cremote>\u002F||' | tr -d '[:space:]'\n```\n\nIf `symbolic-ref` fails, fall back to `git branch --list main master`: use the one that exists; if both or neither exist, ask the user.\n\nIf `git branch --show-current` is empty (detached HEAD), show the current commit (`git rev-parse --short HEAD`) and ask whether to branch from it or switch to the default branch first.\n\nOtherwise, if the current branch is not the default branch, warn the user and ask whether to branch from the current branch or switch to the default branch first.\n\nIf the user wants to switch to the default branch, handle any uncommitted changes appropriately (offer to stash them if present), then run `git checkout \u003Cdefault-branch>`. On any failure, restore stashed changes if applicable and stop.\n\nBefore creating the branch, check that the name doesn't already exist locally or on the remote (`git show-ref`). If it does, ask the user to choose a different name.\n\nCreate the branch:\n\n```bash\ngit checkout -b \u003Cbranch-name>\n```\n\nRestore any stashed changes after the branch is created.\n\n## References\n\n- [Sentry Branch Naming](https:\u002F\u002Fdevelop.sentry.dev\u002Fsdk\u002Fgetting-started\u002Fstandards\u002Fcode-submission\u002F#branch-naming)\n","# Create Branch\n\nCreate a git branch with the correct type prefix and a descriptive name following Sentry conventions.\n\n## Step 1: Get the Username Prefix\n\nRun `gh api user --jq .login` to get the GitHub username.\n\nIf the command fails (e.g. not authenticated), ask the user for their preferred prefix.\n\n## Step 2: Determine the Branch Description\n\n**If `$ARGUMENTS` is provided**, use it as the description of the work.\n\n**If no arguments**, check for local changes:\n\n```bash\ngit diff\ngit diff --cached\ngit status --short\n```\n\n- **Changes exist**: read the diff content to understand what the work is about and generate a description.\n- **No changes**: ask the user what they are about to work on.\n\n## Step 3: Classify the Type\n\nPick the type from this table based on the description:\n\n| Type      | Use when                                                              |\n| --------- | --------------------------------------------------------------------- |\n| `feat`    | New user-facing functionality                                         |\n| `fix`     | Broken behavior now works                                             |\n| `ref`     | Same behavior, different structure                                    |\n| `chore`   | Deps, config, version bumps, updating existing tooling — no new logic |\n| `perf`    | Same behavior, faster                                                 |\n| `style`   | CSS, formatting, visual-only                                          |\n| `docs`    | Documentation only                                                    |\n| `test`    | Tests only                                                            |\n| `ci`      | CI\u002FCD config                                                          |\n| `build`   | Build system                                                          |\n| `meta`    | Repo metadata changes                                                 |\n| `license` | License changes                                                       |\n\nWhen unsure: `feat` for new things (including new scripts, skills, or tools), `ref` for restructuring existing things, `chore` only when updating\u002Fmaintaining something that already exists.\n\n## Step 4: Generate and Propose\n\nBuild the branch name as `\u003Cusername>\u002F\u003Ctype>\u002F\u003Cshort-description>`.\n\nRules for `\u003Cshort-description>`:\n\n- Kebab-case, lowercase\n- 3 to 6 words, concise but clear\n- Describe the change, not file names\n- Only use ASCII letters, digits, and hyphens — no spaces, dots, colons, tildes, or other git-forbidden characters\n\nPresent it to the user and ask if they want to use it, modify it, or change the type.\n\n### Examples\n\n| Work description                           | Branch name                                 |\n| ------------------------------------------ | ------------------------------------------- |\n| Dropdown menu not closing on outside click | `priscila\u002Ffix\u002Fdropdown-not-closing-on-blur` |\n| Adding search to conversations page        | `priscila\u002Ffeat\u002Fadd-search-to-conversations` |\n| Restructuring drawer components            | `priscila\u002Fref\u002Fsimplify-drawer-components`   |\n| Updating test fixtures                     | `priscila\u002Fchore\u002Fupdate-test-fixtures`       |\n| Bumping @sentry\u002Freact to latest version    | `priscila\u002Fchore\u002Fbump-sentry-react`          |\n| Adding a new agent skill                   | `priscila\u002Ffeat\u002Fadd-create-branch-skill`     |\n\n## Step 5: Create the Branch\n\nOnce confirmed, detect the current and default branch:\n\n```bash\ngit branch --show-current\ngit remote | grep -qx origin && echo origin || git remote | head -1\ngit symbolic-ref refs\u002Fremotes\u002F\u003Cremote>\u002FHEAD 2>\u002Fdev\u002Fnull | sed 's|refs\u002Fremotes\u002F\u003Cremote>\u002F||' | tr -d '[:space:]'\n```\n\nIf `symbolic-ref` fails, fall back to `git branch --list main master`: use the one that exists; if both or neither exist, ask the user.\n\nIf `git branch --show-current` is empty (detached HEAD), show the current commit (`git rev-parse --short HEAD`) and ask whether to branch from it or switch to the default branch first.\n\nOtherwise, if the current branch is not the default branch, warn the user and ask whether to branch from the current branch or switch to the default branch first.\n\nIf the user wants to switch to the default branch, handle any uncommitted changes appropriately (offer to stash them if present), then run `git checkout \u003Cdefault-branch>`. On any failure, restore stashed changes if applicable and stop.\n\nBefore creating the branch, check that the name doesn't already exist locally or on the remote (`git show-ref`). If it does, ask the user to choose a different name.\n\nCreate the branch:\n\n```bash\ngit checkout -b \u003Cbranch-name>\n```\n\nRestore any stashed changes after the branch is created.\n\n## References\n\n- [Sentry Branch Naming](https:\u002F\u002Fdevelop.sentry.dev\u002Fsdk\u002Fgetting-started\u002Fstandards\u002Fcode-submission\u002F#branch-naming)\n",{"name":5,"risk":25,"source":31,"description":7,"argument-hint":44},"[optional description of the work]","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fcreate-branch","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill create-branch",{"tool":57,"command":58},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill create-branch",{"tool":60,"command":61},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill create-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fcreate-branch\u002FSKILL.md",true,[],[66,90,115,125,138,157],{"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":77,"publishedAt":39},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[78,79,80,81,82,83,84,85,86,87,88,89],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":39},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[97,98,99,100,101,102,80,103,104,105,106,24,107,108,109,110,111,112,113,114],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","brew","live","data","google","install","read","across","api",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":39},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[122,123,97,107,108,109,110,101,80,112,124,113,114,24,105,104,103,111,102,100],"trend radar","radar","pulse",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":39},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[132,133,134,135,136,137],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":149,"publishedAt":39},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[140,86,150,151,152,89,107,153,154,155,99,156,111],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":39},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[159,164,165,166,111,167,154,168,169,170,171,172],"status","play","go","latest","github","discover","control","cmd","volume"]