skills.rest
jaballer
jaballerCOMMUNITY
Explore all skills by this author →
GitHub

ftf-new-branch

Creates Git branches with conventional prefixes synced to master for WordPress work.

2|Updated Jun 14, 2020
Search Tags:#git#conventional commits#branching#WordPress#workflows
One-click install
npx skills add https://github.com/jaballer/fivetwofive-cw --skill ftf-new-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ftf-new-branch
Source: https://github.com/jaballer/fivetwofive-cw/tree/main/.claude/skills/ftf-new-branch
Command: npx skills add https://github.com/jaballer/fivetwofive-cw --skill ftf-new-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating a proper git branch for new work on the FiveTwoFive WordPress site, reducing the risk of working directly on the master branch and ensuring code integrity.

Core Features & Use Cases

  • Branch Creation: Automatically creates a git branch based on the type of work (feature, fix, refactor, etc.).
  • Pull from Master: Ensures that the new branch is always up-to-date with the master branch.
  • Prefix Matching: Uses conventional commit prefixes to ensure consistency in branch naming.
  • Issue Tracking: Optionally names branches using GitHub issue numbers.
  • Use Case: When beginning a new feature development, this Skill ensures a branch is created with the appropriate prefix and is in sync with the latest master branch.

Quick Start

Use the ftf-new-branch skill to create a new feature branch for issue #123: "Add new contact form functionality".

Frequently Asked Questions about ftf-new-branch

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

FAQPage Schema
How do I automate git branch creation for new WordPress development work?▼

You can automate git branch creation by using a workflow that identifies the work type and generates a branch with conventional commit prefixes. This ensures the new branch is pulled from master and stays in sync.

How do I branch from master with conventional commit prefixes in git?▼

To branch from master with conventional commit prefixes, use an automated workflow that matches the work type (feature, fix, refactor) and creates the branch directly from the updated master branch.

Can I include GitHub issue numbers in my git branch naming workflow?▼

Yes, you can include GitHub issue numbers in your git branch naming. The workflow optionally appends the issue tracking number to the conventional commit prefix to maintain consistent branch names.

What is the best way to prevent working directly on the master branch in WordPress?▼

The best way to prevent working directly on master is to automate the creation of a new git branch before starting development. This enforces code integrity by ensuring all new work happens on a synced, prefixed branch.

Does this branching workflow support feature, fix, and refactor prefixes?▼

Yes, the branching workflow supports feature, fix, and refactor prefixes. It identifies the specific type of work and applies the corresponding conventional commit prefix to standardize branch naming.

Related Skills

Explore More Software Engineering Skills→
cbleckercblecker
5

syncing-branch

Sync a local Git branch with its remote using fork-aware fetch and merge.

Community
Basic
hyperlisthyperlist
271

git-workflow

Enforce Git branching, commit, and pull request standards with automated staging.

Community
Intermediate
CapplequoppeCapplequoppe

merge-completed-work

Merge completed GitLab branches into parent branches after verifying issue closure.

Community
Advanced
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic