skills.rest
signalbeam-io
signalbeam-ioOFFICIAL
Explore all skills by this author →
GitHub

start-work

Creates a feature branch from a GitHub issue and validates the working tree.

2|Updated Dec 9, 2025
Search Tags:#automation#git#workflow#github#branching#issue
One-click install
npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill start-work-signalbeam-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start-work
Source: https://github.com/signalbeam-io/signalbeam-edge/tree/main/.claude/skills/start-work
Command: npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill start-work-signalbeam-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a feature branch from a GitHub issue and set up the working context.

Core Features & Use Cases

  • Automated branch creation: From a GitHub issue number, derive and create a standardized branch name and switch to it from the latest main.
  • Working-context validation: Verify a clean working tree before branching and warn when there are uncommitted changes.
  • Transparent reporting: Provide the new branch name and a summary of the issue tasks to the user.

Quick Start

Call the skill with the issue number to create and check out the feature branch from origin/main.

Frequently Asked Questions about start-work

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

FAQPage Schema
How do I create a feature branch from a GitHub issue?▼

You can create a feature branch from a GitHub issue by providing the issue number to an automated workflow that fetches issue details, generates a standardized branch name, and switches to it from the latest origin/main.

What happens if I have uncommitted changes when creating a branch from an issue?▼

When creating a branch from an issue, the workflow performs working-context validation and will warn you if uncommitted changes exist, ensuring a clean working tree before branching from origin/main.

How do I automate GitHub branch naming conventions for feature work?▼

Automating GitHub branch naming conventions requires fetching issue details to derive a standardized branch name from the issue number, updating the main branch, and switching to the new working context.

Do I need a clean working tree to start feature work from a GitHub issue?▼

Yes, a clean working tree is required to start feature work from a GitHub issue. The automated workflow validates your repository state before updating main and generating the new branch.

What information is reported after switching to a new feature branch?▼

After switching to a new feature branch, transparent reporting provides the new branch name alongside a summary of the GitHub issue tasks to set up your working context for development.

Related Skills

Explore More Software Engineering Skills→
supersuit-techsupersuit-tech
4

conflicts

Fetch and merge the latest main branch while resolving conflicts every 90 seconds.

Official
Advanced
Kushal9889Kushal9889

create-pr

Create a branch, commit changes, and open a pull request via GitHub API.

Community
Advanced
FS-GGFS-GG

pnext-item

Automate claiming, working on, and completing GitHub repository items.

Official
Advanced
thktthkt
11

branch

Generate Git branch names from code changes and ticket numbers.

Community
Intermediate