Create Branch

What it does

The source classifies the kind of change, resolves a useful base and handles local or remote name collisions. It tries to keep branch creation noninteractive while avoiding an unexpected switch away from an existing feature branch. Names are intentionally short and descriptive.

Best for

Teams using Sentry-like branch prefixes that need consistent names for small, independent changes.

Tradeoffs and requirements

Branch naming is a repository convention, not a compatibility requirement of Agent Skills. Automatic inference can misread an unrelated working-tree change. A detached checkout or stale remote state also needs care before choosing the base.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/getsentry/skills/tree/d12f250460ffd961f549dbebf7eeb0cf4afd4c2e/skills/create-branch --skill create-branch

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Network Access — review the source context.
• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

84/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

93/100

93

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

55/100

55

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Inspect the current branch and existing edits, confirm the task’s scope, then select a compatible prefix and base. Check collisions before creating the branch, preserving uncommitted work throughout.

How to judge the result

Verify the resulting branch name and starting commit. Confirm that the working tree still contains the intended files and that the branch is based on the requested state, especially when continuing an existing feature rather than starting from the default branch.