SC-feature-branch

Create a correctly named feature branch from an up-to-date main.

1|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/Cnext-eu/kairos-ontology-toolkit --skill sc-feature-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SC-feature-branch
Source: https://github.com/Cnext-eu/kairos-ontology-toolkit/tree/main/.github/skills/SC-feature-branch
Command: npx skills add https://github.com/Cnext-eu/kairos-ontology-toolkit --skill sc-feature-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a clean, correctly named feature branch from the main branch for new work.

Core Features & Use Cases

  • Enforces a standard branch naming convention for new work
  • Validates repository state (clean working tree, up-to-date main)
  • Guides the user through creation and provides a summary for PRs
  • Handles common edge cases (existing branch, detached HEAD, conflicts)

Quick Start

Create a new feature branch from main following the naming convention and push it to the remote.

Frequently Asked Questions about SC-feature-branch

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

FAQPage Schema
How do I create a git feature branch from main with the correct naming convention?

To create a feature branch from main, this skill enforces standard naming conventions and validates your repository state before guiding you through branch creation and remote push. It checks for a clean working tree and up-to-date main baseline.

What is the best way to ensure my main branch is up-to-date before starting feature development?

The best way to ensure your main branch is up-to-date before feature development is by validating the repository state. This skill checks for a clean working tree and confirms the main branch baseline is current before creating your new feature branch.

How does this workflow handle an existing branch or detached HEAD when creating a feature branch?

This workflow handles edge cases like an existing branch, detached HEAD, or conflicts by guiding you through conflict resolution during feature branch creation. It prevents duplicate branches and ensures a clean baseline before proceeding.

Can I use this feature branch workflow if my git working tree has uncommitted changes?

You cannot use this feature branch workflow if your git working tree has uncommitted changes. The skill validates the repository state and requires a clean working tree to ensure the new feature branch is created from a stable main baseline.

Do I need to manually push my new feature branch to the remote repository?

You do not need to manually push your new feature branch to the remote repository. The skill guides you through the creation process and handles pushing the correctly named branch to the remote, providing a summary for PRs.