[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77S9F4Q9K4GDPCX473AN1AE":3,"skill-same:01M77S9F4Q9K4GDPCX473AN1AE":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77S9F4Q9K4GDPCX473AN1AE","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.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fgit-flow-branch-creator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Intelligent Git Flow branch creator that analyzes git status\u002Fdiff and creates appropriate branches following the nvie Git Flow branching model.\"\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","### 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",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fgit-flow-branch-creator",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill git-flow-branch-creator",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill git-flow-branch-creator",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill git-flow-branch-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fgit-flow-branch-creator\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"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":67,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"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":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]