vcs-branch

Git branch naming convention format and strategy.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "vcs-branch" with this command: npx skills add diegocanepa/agent-skills/diegocanepa-agent-skills-vcs-branch

VCS Branching

Format

<type>/<issue-number>-<short-description>

Types

  • feat/ - New feature
  • fix/ - Bug fix
  • refactor/ - Code refactoring
  • docs/ - Documentation
  • test/ - Tests
  • chore/ - Maintenance

Workflow

  1. Identify: Find the related issue number and platform (GitHub/GitLab).
  2. Drafting:
    • Use lowercase and kebab-case.
    • 3-6 words for description.
  3. MITM Confirmation: ALWAYS present the drafted branch name to the USER for approval before creation.
  4. Execution: 
    git checkout main
git pull origin main
git checkout -b <branch-name>

Guidelines

  • English Only: Branch descriptions must be in English.
  • Sync: Always pull the latest changes from the base branch before creating a new one.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHubOpen in ClawHub

Related Skills

Related by shared tags or category signals.

Automation

skill-improvement

No summary provided by upstream source.

Repository SourceNeeds Review
11-diegocanepa
Automation

mermaid-diagrams

No summary provided by upstream source.

Repository SourceNeeds Review
8-diegocanepa
Automation

add-skill

No summary provided by upstream source.

Repository SourceNeeds Review
8-diegocanepa
Automation

skill-creator

No summary provided by upstream source.

Repository SourceNeeds Review
7-diegocanepa