[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSPV05JSQS2YQG5R70XZ46":3,"skill-same:01M6CSPV05JSQS2YQG5R70XZ46":61},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6CSPV05JSQS2YQG5R70XZ46","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.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fcreate-branch\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"create","create branch","branch","git branch","git","sentry","start","work on","work","use","default","community","switch","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: critical\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## When to Use\n\n- You need to create a new git branch that follows the repository's naming convention.\n- You are starting a new piece of work from the default branch and need help classifying it as `feat`, `fix`, `docs`, or another branch type.\n- You want the branch name proposed from either the task description or the current local diff.\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## When to Use\n\n- You need to create a new git branch that follows the repository's naming convention.\n- You are starting a new piece of work from the default branch and need help classifying it as `feat`, `fix`, `docs`, or another branch type.\n- You want the branch name proposed from either the task description or the current local diff.\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":37,"source":30,"description":7,"argument-hint":38},"critical","[optional description of the work]","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fcreate-branch",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill create-branch",{"tool":53,"command":54},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill create-branch",{"tool":56,"command":57},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill create-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fcreate-branch\u002FSKILL.md",true,[],[62,75,90,116,135,162],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":72,"publishedAt":32},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[67],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[73,74],"Test Skill","test",{"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":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":32},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[82,83,84,85,86,87,88,30,19,89],"zustand store ts","zustand","store","with","types","middleware","patterns","typescript",{"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":99,"publishedAt":32},"01M6GDRKEA0WE670SPFWX5GKCN","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000023","Skill与智能体开发",[100,101,102,103,104,105,106,107,108,109,37,110,111,112,30,113,114,115],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","creation","webinars","composio","recordings","management","tracking",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":32},"01M6GDRFS1452PC71JQ38S24HR","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[122],{"categoryNo":97,"categoryName":98,"taxonomyType":70,"taxonomyTypeDesc":71},[124,100,125,126,127,128,129,30,105,130,112,131,37,109,104,132,19,133,106,134],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":32},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000009","前端开发",[145,146,147,148,149,89,150,151,152,153,154,155,85,156,157,158,159,30,160,161],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":32},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[168],{"categoryNo":97,"categoryName":98,"taxonomyType":70,"taxonomyTypeDesc":71},[170,171,172,173,174,175,176,177,30,178,179,180,181,182,183,184,185,186,187,106],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]