Create Branch

Overview

This public intake copy packages

plugins/antigravity-awesome-skills/skills/create-branch

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Create Branch Create a git branch with the correct type prefix and a descriptive name following Sentry conventions.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• You need to create a new git branch that follows the repository's naming convention.
• 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.
• You want the branch name proposed from either the task description or the current local diff.
• Use when the request clearly matches the imported source intent: 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.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Changes exist: read the diff content to understand what the work is about and generate a description.
2. No changes: ask the user what they are about to work on.
3. Type - Use when
4. feat - New user-facing functionality
5. fix - Broken behavior now works
6. ref - Same behavior, different structure
7. chore - Deps, config, version bumps, updating existing tooling — no new logic

Imported Workflow Notes

Imported: Step 1: Get the Username Prefix

Run

gh api user --jq .login

If the command fails (e.g. not authenticated), ask the user for their preferred prefix.

Imported: Step 2: Determine the Branch Description

If

$ARGUMENTS

If no arguments, check for local changes:

git diff
git diff --cached
git status --short

• Changes exist: read the diff content to understand what the work is about and generate a description.
• No changes: ask the user what they are about to work on.

Imported: Step 3: Classify the Type

Pick the type from this table based on the description:

feat

fix

ref

chore

perf

style

docs

test

ci

build

meta

license

When unsure:

feat

ref

chore

Imported: Step 4: Generate and Propose

Build the branch name as

<username>/<type>/<short-description>

Rules for

<short-description>

• Kebab-case, lowercase
• 3 to 6 words, concise but clear
• Describe the change, not file names
• Only use ASCII letters, digits, and hyphens — no spaces, dots, colons, tildes, or other git-forbidden characters

Present it to the user and ask if they want to use it, modify it, or change the type.

Examples

priscila/fix/dropdown-not-closing-on-blur

priscila/feat/add-search-to-conversations

priscila/ref/simplify-drawer-components

priscila/chore/update-test-fixtures

priscila/chore/bump-sentry-react

priscila/feat/add-create-branch-skill

Imported: Step 5: Create the Branch

Once confirmed, detect the current and default branch:

git branch --show-current
git remote | grep -qx origin && echo origin || git remote | head -1
git symbolic-ref refs/remotes/<remote>/HEAD 2>/dev/null | sed 's|refs/remotes/<remote>/||' | tr -d '[:space:]'

If

symbolic-ref

git branch --list main master

If

git branch --show-current

git rev-parse --short HEAD

Otherwise, 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.

If the user wants to switch to the default branch, handle any uncommitted changes appropriately (offer to stash them if present), then run

git checkout <default-branch>

Before creating the branch, check that the name doesn't already exist locally or on the remote (

git show-ref

Create the branch:

git checkout -b <branch-name>

Restore any stashed changes after the branch is created.

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Examples

Example 1: Ask for the upstream workflow directly

Use @create-branch-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @create-branch-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @create-branch-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @create-branch-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills/skills/create-branch

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @comprehensive-review-pr-enhance-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @computer-use-agents-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @computer-vision-expert-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @concise-planning-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: References

• Sentry Branch Naming