[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F4PFPX069ANXCQ93SWY74M":3,"skill-same:01M6F4PFPX069ANXCQ93SWY74M":56},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M6F4PFPX069ANXCQ93SWY74M","git-flow-branch-creator",null,"Intelligent Git Flow branch creator that analyzes git status\u002Fdiff and creates appropriate branches following the nvie Git Flow branching model.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fgithub\u002Fawesome-copilot\u002Fgit-flow-branch-creator\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"git","git flow branch creator","flow","branch","status","model","diff","branches","branching","2026-11-10 10:12:30",false,"---\nname: git-flow-branch-creator\ndescription: 'Intelligent Git Flow branch creator that analyzes git status\u002Fdiff and creates appropriate branches following the nvie Git Flow branching model.'\n---\n\n### Instructions\n\n```xml\n\u003Cinstructions>\n\t\u003Ctitle>Git Flow Branch Creator\u003C\u002Ftitle>\n\t\u003Cdescription>This prompt analyzes your current git changes using git status and git diff (or git diff --cached), then intelligently determines the appropriate branch type according to the Git Flow branching model and creates a semantic branch name.\u003C\u002Fdescription>\n\t\u003Cnote>\n\t\tJust run this prompt and Copilot will analyze your changes and create the appropriate Git Flow branch for you.\n\t\u003C\u002Fnote>\n\u003C\u002Finstructions>\n```\n\n### Workflow\n\n**Follow these steps:**\n\n1. Run `git status` to review the current repository state and changed files.\n2. Run `git diff` (for unstaged changes) or `git diff --cached` (for staged changes) to analyze the nature of changes.\n3. Analyze the changes using the Git Flow Branch Analysis Framework below.\n4. Determine the appropriate branch type based on the analysis.\n5. Generate a semantic branch name following Git Flow conventions.\n6. Create the branch and switch to it automatically.\n7. Provide a summary of the analysis and next steps.\n\n### Git Flow Branch Analysis Framework\n\n```xml\n\u003Canalysis-framework>\n\t\u003Cbranch-types>\n\t\t\u003Cfeature>\n\t\t\t\u003Cpurpose>New features, enhancements, non-critical improvements\u003C\u002Fpurpose>\n\t\t\t\u003Cbranch-from>develop\u003C\u002Fbranch-from>\n\t\t\t\u003Cmerge-to>develop\u003C\u002Fmerge-to>\n\t\t\t\u003Cnaming>feature\u002Fdescriptive-name or feature\u002Fticket-number-description\u003C\u002Fnaming>\n\t\t\t\u003Cindicators>\n\t\t\t\t\u003Cindicator>New functionality being added\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>UI\u002FUX improvements\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>New API endpoints or methods\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Database schema additions (non-breaking)\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>New configuration options\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Performance improvements (non-critical)\u003C\u002Findicator>\n\t\t\t\u003C\u002Findicators>\n\t\t\u003C\u002Ffeature>\n\n\t\t\u003Crelease>\n\t\t\t\u003Cpurpose>Release preparation, version bumps, final testing\u003C\u002Fpurpose>\n\t\t\t\u003Cbranch-from>develop\u003C\u002Fbranch-from>\n\t\t\t\u003Cmerge-to>develop AND master\u003C\u002Fmerge-to>\n\t\t\t\u003Cnaming>release-X.Y.Z\u003C\u002Fnaming>\n\t\t\t\u003Cindicators>\n\t\t\t\t\u003Cindicator>Version number changes\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Build configuration updates\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Documentation finalization\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Minor bug fixes before release\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Release notes updates\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Dependency version locks\u003C\u002Findicator>\n\t\t\t\u003C\u002Findicators>\n\t\t\u003C\u002Frelease>\n\n\t\t\u003Chotfix>\n\t\t\t\u003Cpurpose>Critical production bug fixes requiring immediate deployment\u003C\u002Fpurpose>\n\t\t\t\u003Cbranch-from>master\u003C\u002Fbranch-from>\n\t\t\t\u003Cmerge-to>develop AND master\u003C\u002Fmerge-to>\n\t\t\t\u003Cnaming>hotfix-X.Y.Z or hotfix\u002Fcritical-issue-description\u003C\u002Fnaming>\n\t\t\t\u003Cindicators>\n\t\t\t\t\u003Cindicator>Security vulnerability fixes\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Critical production bugs\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Data corruption fixes\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Service outage resolution\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Emergency configuration changes\u003C\u002Findicator>\n\t\t\t\u003C\u002Findicators>\n\t\t\u003C\u002Fhotfix>\n\t\u003C\u002Fbranch-types>\n\u003C\u002Fanalysis-framework>\n```\n\n### Branch Naming Conventions\n\n```xml\n\u003Cnaming-conventions>\n\t\u003Cfeature-branches>\n\t\t\u003Cformat>feature\u002F[ticket-number-]descriptive-name\u003C\u002Fformat>\n\t\t\u003Cexamples>\n\t\t\t\u003Cexample>feature\u002Fuser-authentication\u003C\u002Fexample>\n\t\t\t\u003Cexample>feature\u002FPROJ-123-shopping-cart\u003C\u002Fexample>\n\t\t\t\u003Cexample>feature\u002Fapi-rate-limiting\u003C\u002Fexample>\n\t\t\t\u003Cexample>feature\u002Fdashboard-redesign\u003C\u002Fexample>\n\t\t\u003C\u002Fexamples>\n\t\u003C\u002Ffeature-branches>\n\n\t\u003Crelease-branches>\n\t\t\u003Cformat>release-X.Y.Z\u003C\u002Fformat>\n\t\t\u003Cexamples>\n\t\t\t\u003Cexample>release-1.2.0\u003C\u002Fexample>\n\t\t\t\u003Cexample>release-2.1.0\u003C\u002Fexample>\n\t\t\t\u003Cexample>release-1.0.0\u003C\u002Fexample>\n\t\t\u003C\u002Fexamples>\n\t\u003C\u002Frelease-branches>\n\n\t\u003Chotfix-branches>\n\t\t\u003Cformat>hotfix-X.Y.Z OR hotfix\u002Fcritical-description\u003C\u002Fformat>\n\t\t\u003Cexamples>\n\t\t\t\u003Cexample>hotfix-1.2.1\u003C\u002Fexample>\n\t\t\t\u003Cexample>hotfix\u002Fsecurity-patch\u003C\u002Fexample>\n\t\t\t\u003Cexample>hotfix\u002Fpayment-gateway-fix\u003C\u002Fexample>\n\t\t\t\u003Cexample>hotfix-2.1.1\u003C\u002Fexample>\n\t\t\u003C\u002Fexamples>\n\t\u003C\u002Fhotfix-branches>\n\u003C\u002Fnaming-conventions>\n```\n\n### Analysis Process\n\n```xml\n\u003Canalysis-process>\n\t\u003Cstep-1>\n\t\t\u003Ctitle>Change Nature Analysis\u003C\u002Ftitle>\n\t\t\u003Cdescription>Examine the types of files modified and the nature of changes\u003C\u002Fdescription>\n\t\t\u003Ccriteria>\n\t\t\t\u003Cfiles-modified>Look at file extensions, directory structure, and purpose\u003C\u002Ffiles-modified>\n\t\t\t\u003Cchange-scope>Determine if changes are additive, corrective, or preparatory\u003C\u002Fchange-scope>\n\t\t\t\u003Curgency-level>Assess if changes address critical issues or are developmental\u003C\u002Furgency-level>\n\t\t\u003C\u002Fcriteria>\n\t\u003C\u002Fstep-1>\n\n\t\u003Cstep-2>\n\t\t\u003Ctitle>Git Flow Classification\u003C\u002Ftitle>\n\t\t\u003Cdescription>Map the changes to appropriate Git Flow branch type\u003C\u002Fdescription>\n\t\t\u003Cdecision-tree>\n\t\t\t\u003Cquestion>Are these critical fixes for production issues?\u003C\u002Fquestion>\n\t\t\t\u003Cif-yes>Consider hotfix branch\u003C\u002Fif-yes>\n\t\t\t\u003Cif-no>\n\t\t\t\t\u003Cquestion>Are these release preparation changes (version bumps, final tweaks)?\u003C\u002Fquestion>\n\t\t\t\t\u003Cif-yes>Consider release branch\u003C\u002Fif-yes>\n\t\t\t\t\u003Cif-no>Default to feature branch\u003C\u002Fif-no>\n\t\t\t\u003C\u002Fif-no>\n\t\t\u003C\u002Fdecision-tree>\n\t\u003C\u002Fstep-2>\n\n\t\u003Cstep-3>\n\t\t\u003Ctitle>Branch Name Generation\u003C\u002Ftitle>\n\t\t\u003Cdescription>Create semantic, descriptive branch name\u003C\u002Fdescription>\n\t\t\u003Cguidelines>\n\t\t\t\u003Cuse-kebab-case>Use lowercase with hyphens\u003C\u002Fuse-kebab-case>\n\t\t\t\u003Cbe-descriptive>Name should clearly indicate the purpose\u003C\u002Fbe-descriptive>\n\t\t\t\u003Cinclude-context>Add ticket numbers or project context when available\u003C\u002Finclude-context>\n\t\t\t\u003Ckeep-concise>Avoid overly long names\u003C\u002Fkeep-concise>\n\t\t\u003C\u002Fguidelines>\n\t\u003C\u002Fstep-3>\n\u003C\u002Fanalysis-process>\n```\n\n### Edge Cases and Validation\n\n```xml\n\u003Cedge-cases>\n\t\u003Cmixed-changes>\n\t\t\u003Cscenario>Changes include both features and bug fixes\u003C\u002Fscenario>\n\t\t\u003Cresolution>Prioritize the most significant change type or suggest splitting into multiple branches\u003C\u002Fresolution>\n\t\u003C\u002Fmixed-changes>\n\n\t\u003Cno-changes>\n\t\t\u003Cscenario>No changes detected in git status\u002Fdiff\u003C\u002Fscenario>\n\t\t\u003Cresolution>Inform user and suggest checking git status or making changes first\u003C\u002Fresolution>\n\t\u003C\u002Fno-changes>\n\n\t\u003Cexisting-branch>\n\t\t\u003Cscenario>Already on a feature\u002Fhotfix\u002Frelease branch\u003C\u002Fscenario>\n\t\t\u003Cresolution>Analyze if new branch is needed or if current branch is appropriate\u003C\u002Fresolution>\n\t\u003C\u002Fexisting-branch>\n\n\t\u003Cconflicting-names>\n\t\t\u003Cscenario>Suggested branch name already exists\u003C\u002Fscenario>\n\t\t\u003Cresolution>Append incremental suffix or suggest alternative name\u003C\u002Fresolution>\n\t\u003C\u002Fconflicting-names>\n\u003C\u002Fedge-cases>\n```\n\n### Examples\n\n```xml\n\u003Cexamples>\n\t\u003Cexample-1>\n\t\t\u003Cscenario>Added new user registration API endpoint\u003C\u002Fscenario>\n\t\t\u003Canalysis>New functionality, additive changes, not critical\u003C\u002Fanalysis>\n\t\t\u003Cbranch-type>feature\u003C\u002Fbranch-type>\n\t\t\u003Cbranch-name>feature\u002Fuser-registration-api\u003C\u002Fbranch-name>\n\t\t\u003Ccommand>git checkout -b feature\u002Fuser-registration-api develop\u003C\u002Fcommand>\n\t\u003C\u002Fexample-1>\n\n\t\u003Cexample-2>\n\t\t\u003Cscenario>Fixed critical security vulnerability in authentication\u003C\u002Fscenario>\n\t\t\u003Canalysis>Security fix, critical for production, immediate deployment needed\u003C\u002Fanalysis>\n\t\t\u003Cbranch-type>hotfix\u003C\u002Fbranch-type>\n\t\t\u003Cbranch-name>hotfix\u002Fauth-security-patch\u003C\u002Fbranch-name>\n\t\t\u003Ccommand>git checkout -b hotfix\u002Fauth-security-patch master\u003C\u002Fcommand>\n\t\u003C\u002Fexample-2>\n\n\t\u003Cexample-3>\n\t\t\u003Cscenario>Updated version to 2.1.0 and finalized release notes\u003C\u002Fscenario>\n\t\t\u003Canalysis>Release preparation, version bump, documentation\u003C\u002Fanalysis>\n\t\t\u003Cbranch-type>release\u003C\u002Fbranch-type>\n\t\t\u003Cbranch-name>release-2.1.0\u003C\u002Fbranch-name>\n\t\t\u003Ccommand>git checkout -b release-2.1.0 develop\u003C\u002Fcommand>\n\t\u003C\u002Fexample-3>\n\n\t\u003Cexample-4>\n\t\t\u003Cscenario>Improved database query performance and updated caching\u003C\u002Fscenario>\n\t\t\u003Canalysis>Performance improvement, non-critical enhancement\u003C\u002Fanalysis>\n\t\t\u003Cbranch-type>feature\u003C\u002Fbranch-type>\n\t\t\u003Cbranch-name>feature\u002Fdatabase-performance-optimization\u003C\u002Fbranch-name>\n\t\t\u003Ccommand>git checkout -b feature\u002Fdatabase-performance-optimization develop\u003C\u002Fcommand>\n\t\u003C\u002Fexample-4>\n\u003C\u002Fexamples>\n```\n\n### Validation Checklist\n\n```xml\n\u003Cvalidation>\n\t\u003Cpre-analysis>\n\t\t\u003Ccheck>Repository is in a clean state (no uncommitted changes that would conflict)\u003C\u002Fcheck>\n\t\t\u003Ccheck>Current branch is appropriate starting point (develop for features\u002Freleases, master for hotfixes)\u003C\u002Fcheck>\n\t\t\u003Ccheck>Remote repository is up to date\u003C\u002Fcheck>\n\t\u003C\u002Fpre-analysis>\n\n\t\u003Canalysis-quality>\n\t\t\u003Ccheck>Change analysis covers all modified files\u003C\u002Fcheck>\n\t\t\u003Ccheck>Branch type selection follows Git Flow principles\u003C\u002Fcheck>\n\t\t\u003Ccheck>Branch name is semantic and follows conventions\u003C\u002Fcheck>\n\t\t\u003Ccheck>Edge cases are considered and handled\u003C\u002Fcheck>\n\t\u003C\u002Fanalysis-quality>\n\n\t\u003Cexecution-safety>\n\t\t\u003Ccheck>Target branch (develop\u002Fmaster) exists and is accessible\u003C\u002Fcheck>\n\t\t\u003Ccheck>Proposed branch name doesn't conflict with existing branches\u003C\u002Fcheck>\n\t\t\u003Ccheck>User has appropriate permissions to create branches\u003C\u002Fcheck>\n\t\u003C\u002Fexecution-safety>\n\u003C\u002Fvalidation>\n```\n\n### Final Execution\n\n```xml\n\u003Cexecution-protocol>\n\t\u003Canalysis-summary>\n\t\t\u003Cgit-status>Output of git status command\u003C\u002Fgit-status>\n\t\t\u003Cgit-diff>Relevant portions of git diff output\u003C\u002Fgit-diff>\n\t\t\u003Cchange-analysis>Detailed analysis of what changes represent\u003C\u002Fchange-analysis>\n\t\t\u003Cbranch-decision>Explanation of why specific branch type was chosen\u003C\u002Fbranch-decision>\n\t\u003C\u002Fanalysis-summary>\n\n\t\u003Cbranch-creation>\n\t\t\u003Ccommand>git checkout -b [branch-name] [source-branch]\u003C\u002Fcommand>\n\t\t\u003Cconfirmation>Verify branch creation and current branch status\u003C\u002Fconfirmation>\n\t\t\u003Cnext-steps>Provide guidance on next actions (commit changes, push branch, etc.)\u003C\u002Fnext-steps>\n\t\u003C\u002Fbranch-creation>\n\n\t\u003Cfallback-options>\n\t\t\u003Calternative-names>Suggest 2-3 alternative branch names if primary suggestion isn't suitable\u003C\u002Falternative-names>\n\t\t\u003Cmanual-override>Allow user to specify different branch type if analysis seems incorrect\u003C\u002Fmanual-override>\n\t\u003C\u002Ffallback-options>\n\u003C\u002Fexecution-protocol>\n```\n\n### Git Flow Reference\n\n```xml\n\u003Cgitflow-reference>\n\t\u003Cmain-branches>\n\t\t\u003Cmaster>Production-ready code, every commit is a release\u003C\u002Fmaster>\n\t\t\u003Cdevelop>Integration branch for features, latest development changes\u003C\u002Fdevelop>\n\t\u003C\u002Fmain-branches>\n\n\t\u003Csupporting-branches>\n\t\t\u003Cfeature>Branch from develop, merge back to develop\u003C\u002Ffeature>\n\t\t\u003Crelease>Branch from develop, merge to both develop and master\u003C\u002Frelease>\n\t\t\u003Chotfix>Branch from master, merge to both develop and master\u003C\u002Fhotfix>\n\t\u003C\u002Fsupporting-branches>\n\n\t\u003Cmerge-strategy>\n\t\t\u003Cflag>Always use --no-ff flag to preserve branch history\u003C\u002Fflag>\n\t\t\u003Ctagging>Tag releases on master branch\u003C\u002Ftagging>\n\t\t\u003Ccleanup>Delete branches after successful merge\u003C\u002Fcleanup>\n\t\u003C\u002Fmerge-strategy>\n\u003C\u002Fgitflow-reference>\n```\n\n","### Instructions\n\n```xml\n\u003Cinstructions>\n\t\u003Ctitle>Git Flow Branch Creator\u003C\u002Ftitle>\n\t\u003Cdescription>This prompt analyzes your current git changes using git status and git diff (or git diff --cached), then intelligently determines the appropriate branch type according to the Git Flow branching model and creates a semantic branch name.\u003C\u002Fdescription>\n\t\u003Cnote>\n\t\tJust run this prompt and Copilot will analyze your changes and create the appropriate Git Flow branch for you.\n\t\u003C\u002Fnote>\n\u003C\u002Finstructions>\n```\n\n### Workflow\n\n**Follow these steps:**\n\n1. Run `git status` to review the current repository state and changed files.\n2. Run `git diff` (for unstaged changes) or `git diff --cached` (for staged changes) to analyze the nature of changes.\n3. Analyze the changes using the Git Flow Branch Analysis Framework below.\n4. Determine the appropriate branch type based on the analysis.\n5. Generate a semantic branch name following Git Flow conventions.\n6. Create the branch and switch to it automatically.\n7. Provide a summary of the analysis and next steps.\n\n### Git Flow Branch Analysis Framework\n\n```xml\n\u003Canalysis-framework>\n\t\u003Cbranch-types>\n\t\t\u003Cfeature>\n\t\t\t\u003Cpurpose>New features, enhancements, non-critical improvements\u003C\u002Fpurpose>\n\t\t\t\u003Cbranch-from>develop\u003C\u002Fbranch-from>\n\t\t\t\u003Cmerge-to>develop\u003C\u002Fmerge-to>\n\t\t\t\u003Cnaming>feature\u002Fdescriptive-name or feature\u002Fticket-number-description\u003C\u002Fnaming>\n\t\t\t\u003Cindicators>\n\t\t\t\t\u003Cindicator>New functionality being added\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>UI\u002FUX improvements\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>New API endpoints or methods\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Database schema additions (non-breaking)\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>New configuration options\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Performance improvements (non-critical)\u003C\u002Findicator>\n\t\t\t\u003C\u002Findicators>\n\t\t\u003C\u002Ffeature>\n\n\t\t\u003Crelease>\n\t\t\t\u003Cpurpose>Release preparation, version bumps, final testing\u003C\u002Fpurpose>\n\t\t\t\u003Cbranch-from>develop\u003C\u002Fbranch-from>\n\t\t\t\u003Cmerge-to>develop AND master\u003C\u002Fmerge-to>\n\t\t\t\u003Cnaming>release-X.Y.Z\u003C\u002Fnaming>\n\t\t\t\u003Cindicators>\n\t\t\t\t\u003Cindicator>Version number changes\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Build configuration updates\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Documentation finalization\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Minor bug fixes before release\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Release notes updates\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Dependency version locks\u003C\u002Findicator>\n\t\t\t\u003C\u002Findicators>\n\t\t\u003C\u002Frelease>\n\n\t\t\u003Chotfix>\n\t\t\t\u003Cpurpose>Critical production bug fixes requiring immediate deployment\u003C\u002Fpurpose>\n\t\t\t\u003Cbranch-from>master\u003C\u002Fbranch-from>\n\t\t\t\u003Cmerge-to>develop AND master\u003C\u002Fmerge-to>\n\t\t\t\u003Cnaming>hotfix-X.Y.Z or hotfix\u002Fcritical-issue-description\u003C\u002Fnaming>\n\t\t\t\u003Cindicators>\n\t\t\t\t\u003Cindicator>Security vulnerability fixes\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Critical production bugs\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Data corruption fixes\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Service outage resolution\u003C\u002Findicator>\n\t\t\t\t\u003Cindicator>Emergency configuration changes\u003C\u002Findicator>\n\t\t\t\u003C\u002Findicators>\n\t\t\u003C\u002Fhotfix>\n\t\u003C\u002Fbranch-types>\n\u003C\u002Fanalysis-framework>\n```\n\n### Branch Naming Conventions\n\n```xml\n\u003Cnaming-conventions>\n\t\u003Cfeature-branches>\n\t\t\u003Cformat>feature\u002F[ticket-number-]descriptive-name\u003C\u002Fformat>\n\t\t\u003Cexamples>\n\t\t\t\u003Cexample>feature\u002Fuser-authentication\u003C\u002Fexample>\n\t\t\t\u003Cexample>feature\u002FPROJ-123-shopping-cart\u003C\u002Fexample>\n\t\t\t\u003Cexample>feature\u002Fapi-rate-limiting\u003C\u002Fexample>\n\t\t\t\u003Cexample>feature\u002Fdashboard-redesign\u003C\u002Fexample>\n\t\t\u003C\u002Fexamples>\n\t\u003C\u002Ffeature-branches>\n\n\t\u003Crelease-branches>\n\t\t\u003Cformat>release-X.Y.Z\u003C\u002Fformat>\n\t\t\u003Cexamples>\n\t\t\t\u003Cexample>release-1.2.0\u003C\u002Fexample>\n\t\t\t\u003Cexample>release-2.1.0\u003C\u002Fexample>\n\t\t\t\u003Cexample>release-1.0.0\u003C\u002Fexample>\n\t\t\u003C\u002Fexamples>\n\t\u003C\u002Frelease-branches>\n\n\t\u003Chotfix-branches>\n\t\t\u003Cformat>hotfix-X.Y.Z OR hotfix\u002Fcritical-description\u003C\u002Fformat>\n\t\t\u003Cexamples>\n\t\t\t\u003Cexample>hotfix-1.2.1\u003C\u002Fexample>\n\t\t\t\u003Cexample>hotfix\u002Fsecurity-patch\u003C\u002Fexample>\n\t\t\t\u003Cexample>hotfix\u002Fpayment-gateway-fix\u003C\u002Fexample>\n\t\t\t\u003Cexample>hotfix-2.1.1\u003C\u002Fexample>\n\t\t\u003C\u002Fexamples>\n\t\u003C\u002Fhotfix-branches>\n\u003C\u002Fnaming-conventions>\n```\n\n### Analysis Process\n\n```xml\n\u003Canalysis-process>\n\t\u003Cstep-1>\n\t\t\u003Ctitle>Change Nature Analysis\u003C\u002Ftitle>\n\t\t\u003Cdescription>Examine the types of files modified and the nature of changes\u003C\u002Fdescription>\n\t\t\u003Ccriteria>\n\t\t\t\u003Cfiles-modified>Look at file extensions, directory structure, and purpose\u003C\u002Ffiles-modified>\n\t\t\t\u003Cchange-scope>Determine if changes are additive, corrective, or preparatory\u003C\u002Fchange-scope>\n\t\t\t\u003Curgency-level>Assess if changes address critical issues or are developmental\u003C\u002Furgency-level>\n\t\t\u003C\u002Fcriteria>\n\t\u003C\u002Fstep-1>\n\n\t\u003Cstep-2>\n\t\t\u003Ctitle>Git Flow Classification\u003C\u002Ftitle>\n\t\t\u003Cdescription>Map the changes to appropriate Git Flow branch type\u003C\u002Fdescription>\n\t\t\u003Cdecision-tree>\n\t\t\t\u003Cquestion>Are these critical fixes for production issues?\u003C\u002Fquestion>\n\t\t\t\u003Cif-yes>Consider hotfix branch\u003C\u002Fif-yes>\n\t\t\t\u003Cif-no>\n\t\t\t\t\u003Cquestion>Are these release preparation changes (version bumps, final tweaks)?\u003C\u002Fquestion>\n\t\t\t\t\u003Cif-yes>Consider release branch\u003C\u002Fif-yes>\n\t\t\t\t\u003Cif-no>Default to feature branch\u003C\u002Fif-no>\n\t\t\t\u003C\u002Fif-no>\n\t\t\u003C\u002Fdecision-tree>\n\t\u003C\u002Fstep-2>\n\n\t\u003Cstep-3>\n\t\t\u003Ctitle>Branch Name Generation\u003C\u002Ftitle>\n\t\t\u003Cdescription>Create semantic, descriptive branch name\u003C\u002Fdescription>\n\t\t\u003Cguidelines>\n\t\t\t\u003Cuse-kebab-case>Use lowercase with hyphens\u003C\u002Fuse-kebab-case>\n\t\t\t\u003Cbe-descriptive>Name should clearly indicate the purpose\u003C\u002Fbe-descriptive>\n\t\t\t\u003Cinclude-context>Add ticket numbers or project context when available\u003C\u002Finclude-context>\n\t\t\t\u003Ckeep-concise>Avoid overly long names\u003C\u002Fkeep-concise>\n\t\t\u003C\u002Fguidelines>\n\t\u003C\u002Fstep-3>\n\u003C\u002Fanalysis-process>\n```\n\n### Edge Cases and Validation\n\n```xml\n\u003Cedge-cases>\n\t\u003Cmixed-changes>\n\t\t\u003Cscenario>Changes include both features and bug fixes\u003C\u002Fscenario>\n\t\t\u003Cresolution>Prioritize the most significant change type or suggest splitting into multiple branches\u003C\u002Fresolution>\n\t\u003C\u002Fmixed-changes>\n\n\t\u003Cno-changes>\n\t\t\u003Cscenario>No changes detected in git status\u002Fdiff\u003C\u002Fscenario>\n\t\t\u003Cresolution>Inform user and suggest checking git status or making changes first\u003C\u002Fresolution>\n\t\u003C\u002Fno-changes>\n\n\t\u003Cexisting-branch>\n\t\t\u003Cscenario>Already on a feature\u002Fhotfix\u002Frelease branch\u003C\u002Fscenario>\n\t\t\u003Cresolution>Analyze if new branch is needed or if current branch is appropriate\u003C\u002Fresolution>\n\t\u003C\u002Fexisting-branch>\n\n\t\u003Cconflicting-names>\n\t\t\u003Cscenario>Suggested branch name already exists\u003C\u002Fscenario>\n\t\t\u003Cresolution>Append incremental suffix or suggest alternative name\u003C\u002Fresolution>\n\t\u003C\u002Fconflicting-names>\n\u003C\u002Fedge-cases>\n```\n\n### Examples\n\n```xml\n\u003Cexamples>\n\t\u003Cexample-1>\n\t\t\u003Cscenario>Added new user registration API endpoint\u003C\u002Fscenario>\n\t\t\u003Canalysis>New functionality, additive changes, not critical\u003C\u002Fanalysis>\n\t\t\u003Cbranch-type>feature\u003C\u002Fbranch-type>\n\t\t\u003Cbranch-name>feature\u002Fuser-registration-api\u003C\u002Fbranch-name>\n\t\t\u003Ccommand>git checkout -b feature\u002Fuser-registration-api develop\u003C\u002Fcommand>\n\t\u003C\u002Fexample-1>\n\n\t\u003Cexample-2>\n\t\t\u003Cscenario>Fixed critical security vulnerability in authentication\u003C\u002Fscenario>\n\t\t\u003Canalysis>Security fix, critical for production, immediate deployment needed\u003C\u002Fanalysis>\n\t\t\u003Cbranch-type>hotfix\u003C\u002Fbranch-type>\n\t\t\u003Cbranch-name>hotfix\u002Fauth-security-patch\u003C\u002Fbranch-name>\n\t\t\u003Ccommand>git checkout -b hotfix\u002Fauth-security-patch master\u003C\u002Fcommand>\n\t\u003C\u002Fexample-2>\n\n\t\u003Cexample-3>\n\t\t\u003Cscenario>Updated version to 2.1.0 and finalized release notes\u003C\u002Fscenario>\n\t\t\u003Canalysis>Release preparation, version bump, documentation\u003C\u002Fanalysis>\n\t\t\u003Cbranch-type>release\u003C\u002Fbranch-type>\n\t\t\u003Cbranch-name>release-2.1.0\u003C\u002Fbranch-name>\n\t\t\u003Ccommand>git checkout -b release-2.1.0 develop\u003C\u002Fcommand>\n\t\u003C\u002Fexample-3>\n\n\t\u003Cexample-4>\n\t\t\u003Cscenario>Improved database query performance and updated caching\u003C\u002Fscenario>\n\t\t\u003Canalysis>Performance improvement, non-critical enhancement\u003C\u002Fanalysis>\n\t\t\u003Cbranch-type>feature\u003C\u002Fbranch-type>\n\t\t\u003Cbranch-name>feature\u002Fdatabase-performance-optimization\u003C\u002Fbranch-name>\n\t\t\u003Ccommand>git checkout -b feature\u002Fdatabase-performance-optimization develop\u003C\u002Fcommand>\n\t\u003C\u002Fexample-4>\n\u003C\u002Fexamples>\n```\n\n### Validation Checklist\n\n```xml\n\u003Cvalidation>\n\t\u003Cpre-analysis>\n\t\t\u003Ccheck>Repository is in a clean state (no uncommitted changes that would conflict)\u003C\u002Fcheck>\n\t\t\u003Ccheck>Current branch is appropriate starting point (develop for features\u002Freleases, master for hotfixes)\u003C\u002Fcheck>\n\t\t\u003Ccheck>Remote repository is up to date\u003C\u002Fcheck>\n\t\u003C\u002Fpre-analysis>\n\n\t\u003Canalysis-quality>\n\t\t\u003Ccheck>Change analysis covers all modified files\u003C\u002Fcheck>\n\t\t\u003Ccheck>Branch type selection follows Git Flow principles\u003C\u002Fcheck>\n\t\t\u003Ccheck>Branch name is semantic and follows conventions\u003C\u002Fcheck>\n\t\t\u003Ccheck>Edge cases are considered and handled\u003C\u002Fcheck>\n\t\u003C\u002Fanalysis-quality>\n\n\t\u003Cexecution-safety>\n\t\t\u003Ccheck>Target branch (develop\u002Fmaster) exists and is accessible\u003C\u002Fcheck>\n\t\t\u003Ccheck>Proposed branch name doesn't conflict with existing branches\u003C\u002Fcheck>\n\t\t\u003Ccheck>User has appropriate permissions to create branches\u003C\u002Fcheck>\n\t\u003C\u002Fexecution-safety>\n\u003C\u002Fvalidation>\n```\n\n### Final Execution\n\n```xml\n\u003Cexecution-protocol>\n\t\u003Canalysis-summary>\n\t\t\u003Cgit-status>Output of git status command\u003C\u002Fgit-status>\n\t\t\u003Cgit-diff>Relevant portions of git diff output\u003C\u002Fgit-diff>\n\t\t\u003Cchange-analysis>Detailed analysis of what changes represent\u003C\u002Fchange-analysis>\n\t\t\u003Cbranch-decision>Explanation of why specific branch type was chosen\u003C\u002Fbranch-decision>\n\t\u003C\u002Fanalysis-summary>\n\n\t\u003Cbranch-creation>\n\t\t\u003Ccommand>git checkout -b [branch-name] [source-branch]\u003C\u002Fcommand>\n\t\t\u003Cconfirmation>Verify branch creation and current branch status\u003C\u002Fconfirmation>\n\t\t\u003Cnext-steps>Provide guidance on next actions (commit changes, push branch, etc.)\u003C\u002Fnext-steps>\n\t\u003C\u002Fbranch-creation>\n\n\t\u003Cfallback-options>\n\t\t\u003Calternative-names>Suggest 2-3 alternative branch names if primary suggestion isn't suitable\u003C\u002Falternative-names>\n\t\t\u003Cmanual-override>Allow user to specify different branch type if analysis seems incorrect\u003C\u002Fmanual-override>\n\t\u003C\u002Ffallback-options>\n\u003C\u002Fexecution-protocol>\n```\n\n### Git Flow Reference\n\n```xml\n\u003Cgitflow-reference>\n\t\u003Cmain-branches>\n\t\t\u003Cmaster>Production-ready code, every commit is a release\u003C\u002Fmaster>\n\t\t\u003Cdevelop>Integration branch for features, latest development changes\u003C\u002Fdevelop>\n\t\u003C\u002Fmain-branches>\n\n\t\u003Csupporting-branches>\n\t\t\u003Cfeature>Branch from develop, merge back to develop\u003C\u002Ffeature>\n\t\t\u003Crelease>Branch from develop, merge to both develop and master\u003C\u002Frelease>\n\t\t\u003Chotfix>Branch from master, merge to both develop and master\u003C\u002Fhotfix>\n\t\u003C\u002Fsupporting-branches>\n\n\t\u003Cmerge-strategy>\n\t\t\u003Cflag>Always use --no-ff flag to preserve branch history\u003C\u002Fflag>\n\t\t\u003Ctagging>Tag releases on master branch\u003C\u002Ftagging>\n\t\t\u003Ccleanup>Delete branches after successful merge\u003C\u002Fcleanup>\n\t\u003C\u002Fmerge-strategy>\n\u003C\u002Fgitflow-reference>\n```\n\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Fgithub\u002Fawesome-copilot\u002Fgit-flow-branch-creator",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill git-flow-branch-creator",{"tool":48,"command":49},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill git-flow-branch-creator",{"tool":51,"command":52},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill git-flow-branch-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fgithub\u002Fawesome-copilot\u002Fgit-flow-branch-creator\u002FSKILL.md",true,[],[57,70,80,89,95,102],{"skillNo":58,"name":59,"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":60,"categories":61,"keywords":67,"publishedAt":28},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[62],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,68,69],"model hierarchy","model hierarchy skill",{"skillNo":71,"name":72,"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":73,"categories":74,"keywords":76,"publishedAt":28},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[75],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[77,78,79],"MCP","zoom","zoom mcp",{"skillNo":81,"name":82,"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":83,"categories":84,"keywords":85,"publishedAt":28},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[86,87,88,78],"sdk","zoom apps sdk","apps",{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":28},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[91],{"skillNo":96,"name":97,"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":98,"categories":99,"keywords":101,"publishedAt":28},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[100],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[97],{"skillNo":103,"name":104,"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":105,"categories":106,"keywords":107,"publishedAt":28},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[104]]