Branch

Name: Branch
Availability: InStock
Author: intrale

Create Git branches from origin/main using issue IDs and slugs.

1|Updated Jun 26, 2025

Search Tags:#git #workflow #development #code review #security #branching

Ready to run

npx skills add https://github.com/intrale/platform --skill branch-intrale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Branch
Source: https://github.com/intrale/platform/tree/main/.claude/skills/branch
Command: npx skills add https://github.com/intrale/platform --skill branch-intrale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enforces safe Git branching practices, preventing direct commits to the main branch and ensuring a professional, secure development workflow.

Core Features & Use Cases

Branch Creation: Creates new feature branches based on issue numbers and descriptive slugs.
Status Checks: Verifies that the current branch is not main and adheres to naming conventions.
Workflow Enforcement: Guards against unsafe Git operations and promotes a clean commit history.
Use Case: Before starting new development, use this Skill to create a dedicated branch like agent/123-fix-login-bug, ensuring all work is isolated and traceable.

Quick Start

Use the branch skill to create a new branch for issue 456 with the slug 'update-readme'.

Frequently Asked Questions about Branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent direct commits to the main branch in a Git workflow?▼

To prevent direct commits to the main branch, you can use Git workflow enforcement to validate branch creation and ensure all development happens on isolated branches. This Skill automatically checks branch status and blocks unsafe operations, guarding the main branch.

What is a secure Git branching strategy for tracking issue IDs?▼

A secure Git branching strategy links branch names to issue tracking IDs and descriptive slugs. This ensures traceability by creating dedicated branches like `agent/123-fix-login-bug` directly from `origin/main`, isolating features and maintaining a clean commit history.

How do I create a new Git feature branch with a specific naming convention?▼

To create a new Git feature branch with naming conventions, specify an issue tracking ID and a descriptive slug. This Skill generates standardized branch names like `agent/456-update-readme` from `origin/main`, enforcing project-specific rules for secure development workflows.

Can I check if my current Git branch adheres to project naming conventions?▼

Yes, you can check if your current Git branch adheres to naming conventions by running a status check. This Skill verifies that the active branch is not `main` and reports the current Git state relative to the main branch to ensure compliance.

Does this Git workflow enforcement tool require any external dependencies?▼

No, this Git workflow enforcement tool does not require any external dependencies. It operates independently using built-in scripts to manage branch creation, validate naming conventions, and report Git state without additional packages.

What happens if I try to commit directly to main during code review?▼

If you try to commit directly to main during code review, the workflow enforcement prevents the unsafe Git operation. It validates that the current branch is not `main`, ensuring all commits are isolated on properly named feature branches before integration.