AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Git Branch

skill-puku0x-agent-skills-test-git-branch · by puku0x

Create Git branches with automatic type detection and project-specific naming conventions. Use when asked to "create a branch", "make a new branch", "create branch for changes", or when ready to organize code changes into a new branch. Supports feat, fix, docs, refactor, test, build, ci, chore, revert, and perf branch types with automatic type selection based on changed file patterns.

↗ Repository
— No reviews yet
0 installs
39 views
0.0% view→install

Install

$ agentstack add skill-puku0x-agent-skills-test-git-branch

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-puku0x-agent-skills-test-git-branch)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Git Branch? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Git Branch Skill

This skill guides the creation of Git branches with project-specific naming conventions.

When to Use

Use this skill when:

  • You have made changes to the codebase and need to create a new branch for those changes.
  • You want to ensure that the branch name follows the project's naming conventions.

Instructions

Step 1: Check staged changes

Use the following command to view staged changes:

git diff --staged

Important If there are staged changes, proceed to the next step.

If there are no staged changes, check unstaged changes with:

git diff --name-only

Step 2: Determine branch type and description

The format for branch names is:

-
  • If there are only staged changes, base the branch name on the staged changes.
  • If there are only unstaged changes, base the branch name on the unstaged changes.
  • If there are both staged and unstaged changes, base the branch name on the staged changes.

type is determined based on the patterns of the changed files:

  • feat-: New features or changes to existing features
  • fix-: Bug fixes
  • refactor-: Refactoring (changes that do not add features or fix bugs)
  • test-: Adding or modifying tests (e.g., changes to *.spec.* or *.spec.*.snap files)
  • docs-: Documentation-only changes (e.g., changes to *.md files)
  • ci-: CI-related changes (e.g., changes to files in .github/workflows/* or .github/actions/*)
  • chore-: Other changes (e.g., changes to *.json, configuration files like *.config.js, .gitignore, etc.)
  • revert-: Reverting previous commits
  • build-: Changes related to the build system or external dependencies
  • perf-: Performance improvements

description should concisely describe the changes made, using hyphens to separate words.

Step 3: Create the branch

Use git switch -c to create and switch to the new branch.

Example:

git switch -c feat-user-authentication

> [!NOTE] > > When the name of the branch already exists, append a unique suffix to the branch name to avoid conflicts. For example, if feat-user-authentication already exists, create feat-user-authentication-1, feat-user-authentication-2, etc.

References

  • [branch-name.md](./references/branch-name.md)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools