--- title: "Sentry create branch: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/skills/getsentry-create-branch/ description: "Creates one local branch with git checkout -b and does not say to push or to commit." --- # Sentry create branch: review, setup & limitations · Undominated.ai > Creates one local branch with git checkout -b and does not say to push or to commit. [← Explore all skills](/skills/) GIT BRANCHES / Functional Software, Inc. dba Sentry # Sentry create branch Creates one local branch with git checkout -b and does not say to push or to commit. [See setup guidance ↓](#setup)[Original source ↗](https://github.com/getsentry/skills/tree/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/create-branch) SOURCE REVIEW Reviewed 2026-10-15 Evidence 3 linked sources Publisher Functional Software, Inc. dba Sentry Licence [Apache-2.0 ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE) Revision d18b7aa8ba87 [Read what was—and wasn’t—checked ↓](#review) “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.” [Functional Software, Inc. dba Sentry · upstream description ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/create-branch/SKILL.md) Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - The workflow creates the branch without asking for a name confirmation, and it only checks out the default branch when the user says so. - Descriptions are constrained to ASCII kebab-case, and a name that already exists locally or on the remote gets a numeric suffix instead of a second prompt. ### A good fit for - Starting a Sentry-style type/description branch from the current work or from an empty tree. - Avoiding an accidental checkout of main when the user is already on a feature branch. - Create a new work branch without silently moving unrelated changes to a different base. - Derive a branch description from both staged and unstaged changes when no work description is supplied. ### Weigh up before choosing - With no local diff it invents a generic description such as repo-maintenance. It does not commit, push, or open a pull request. - Remote collision checks need the git remote. They do not create the remote branch. - This review did not execute the resource. - The workflow can branch from the current non-default branch or detached commit; that is not proof the branch starts at the intended remote base. Remote-name collision checks can be stale without current refs. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - skills/create-branch/SKILL.md - LICENSE - README.md - vercel-labs/skills@48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e:README.md ### Our findings - It runs git checkout -b and reports the name without waiting. It does not push the new branch. - The base stays on the current non-default branch unless the user asks to switch. Default-branch detection falls back from the remote HEAD to main, then master. - It does not commit the diff it may have read in order to name the branch. - The source explicitly avoids switching to the default branch unless requested and defines collision suffixes and detached-HEAD handling. - Description discovery reads git diff, git diff --cached, and git status --short when arguments are absent, so staged-only changes are part of the naming input. ### Not established by this review - The resource was not executed and its tools were not called. - No branch was created in this review. - Not executed: it was not installed or run. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Add a skill to your workflow. [Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/README.md) DOCUMENTED COMMAND npx skills add getsentry/skills/skills/create-branch Copy command ↗ Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above. Optional: install the reviewed revision Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose. npx skills add https://github.com/getsentry/skills/tree/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/create-branch Copy reviewed-revision command ↗ - The command pins only this skill at the reviewed commit. The installer was not executed. - Do not install the whole repository. That would install skills this review did not select. - For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/getsentry-create-branch/bundle.zip and extract it into a new directory. It holds SKILL.md unchanged at revision d18b7aa8, the upstream licence and an attribution file. - Place the extracted directory in your host's documented skills directory, named create-branch. Keep SKILL.md and the licence together. ### Before you start - Node.js and npm - Permission to change the checkout the skill names ### Compatibility Agent Skills hosts · A git or GitHub checkout you are allowed to change ### Implementation Markdown ### Prompt text that tells the agent to create a local branch. It does not say to push or to commit. - Read git status and the diff - Create one local branch - Read the remote HEAD name - Creates and switches local Git branches; preserves existing uncommitted work and does not publish the branch. ### Cost model Apache-2.0 instructions at no charge. Copyright 2025 Functional Software, Inc. dba Sentry. THE COMPLETE REVIEWED DEFINITION ## Read it before you reuse it. Original source bytes, with attribution. Review the host-specific setup notes above. Copy definition ↗ [Download definition + licence ↗](/resources/skills/getsentry-create-branch/bundle.zip)[Raw Markdown ↗](/resources/skills/getsentry-create-branch/definition.md) --- name: create-branch description: 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. argument-hint: '[optional description of the work]' --- # Create Branch Create a git branch following Sentry naming conventions. Keep this workflow non-interactive unless the user explicitly asks to choose the name manually. ## Workflow 1. Resolve the work description: - If `$ARGUMENTS` is present, use it - Otherwise inspect: ```bash git diff git diff --cached git status --short ``` - If there are local changes, derive a short description from the diff - If there are no local changes, use a generic description like `repo-maintenance`, `tooling-update`, or `work-in-progress` 2. Classify the branch type: | Type | Use when | |------|----------| | `feat` | New functionality | | `fix` | Broken behavior now works | | `ref` | Behavior stays the same, structure changes | | `chore` | Maintenance of existing tooling/config | | `perf` | Same behavior, faster | | `style` | Visual or formatting only | | `docs` | Documentation only | | `test` | Tests only | | `ci` | CI/CD config | | `build` | Build system | | `meta` | Repo metadata | | `license` | License changes | When unsure: use `feat` for new things, `ref` for restructuring, `chore` for maintenance. 3. Generate `/`. Keep `` kebab-case, ASCII-only, and ideally 3 to 6 words. 4. Choose the base without prompting: ```bash git branch --show-current git remote | grep -qx origin && echo origin || git remote | head -1 git symbolic-ref refs/remotes//HEAD 2>/dev/null | sed 's|refs/remotes//||' | tr -d '[:space:]' ``` - If default branch detection fails, fall back to `main`, then `master`, then the current branch - If on a detached HEAD, branch from the current commit - If already on a non-default branch, branch from the current branch - Only switch to the default branch when the user explicitly asks 5. Avoid collisions by appending `-2`, `-3`, and so on until the name is unused locally and remotely. 6. Create the branch: ```bash git checkout -b ``` Report the final branch name, but do not stop for confirmation. ## References - [Sentry Branch Naming](https://develop.sentry.dev/sdk/getting-started/standards/code-submission/#branch-naming) The download contains SKILL.md . Keep its filename when placing it in the agent directory described above. By **Functional Software, Inc. dba Sentry**. [Exact upstream source ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/create-branch/SKILL.md) · [Licence](/resources/skills/getsentry-create-branch/LICENSE.txt) · [Attribution](/resources/skills/getsentry-create-branch/ATTRIBUTION.txt) SHA-256 0e017d30c6031477fe147a39e7f40603acb6588ed2a00145c5cd46980a43c6cf Read the applicable licence Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 Functional Software, Inc. dba Sentry Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Sentry create branch ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/create-branch/SKILL.md) Checked 2026-10-14 https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/create-branch/SKILL.md Supports: summary, whySelected, limitations - [Apache-2.0 licence ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE) Checked 2026-10-14 https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE Supports: Redistribution terms, Copyright 2025 Functional Software, Inc. dba Sentry - [Pinned definition review, 2026-10-15 ↗](https://raw.githubusercontent.com/getsentry/skills/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/create-branch/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/getsentry/skills/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/create-branch/SKILL.md Supports: review.findings, bestFor KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Sentry commit message ↗ Drafts one conventional commit on a feature branch, and stops if the branch is still main or master.](/skills/getsentry-commit/)[### Conventional Branch ↗ Creates and validates Git branches against the Conventional Branch specification — feature/, bugfix/, hotfix/, release/, chore/ — with a validation ruleset, an invalid-example table, trunk detection and a mapping to Conventional Commits.](/skills/github-conventional-branch/)[### Django performance review ↗ Review Django code and report only performance issues the reviewer traced. Zero findings is an allowed result.](/skills/getsentry-django-perf-review/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Choose a toolkit](/tools/) - [Inspect execution hosts](/agents/) - [Check tool access](/mcp-servers/) - [Check project dependencies](/check-repo/)