forge-start

Creates a feature branch from synced main and scaffolds delivery templates for a GitHub issue.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill forge-start-jp5labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-start
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/forge-start
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill forge-start-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation on a GitHub issue often involves manual, error-prone setup: syncing main, deriving a branch name, assigning the issue, and preparing delivery templates. Skipping these steps leads to branches cut from stale main, merge conflicts, and missing delivery artifacts. ## Core Features & Use Cases - Branch Setup from Fresh Main: Fetches and fast-forwards local main, then creates a feature branch named issue-<number>-<slug> derived from the issue title. - Issue Claiming and Anchoring: Auto-assigns the issue to the current bot via gh and writes the issue number to tmp/.session-issue so telemetry hooks know where to post. - Delivery Template Scaffolding: Runs jp5 deliver init to generate pr-body.md and issue-comment.md templates under tmp/issue-delivery/<number>/. - Use Case: After a plan for issue #153 is approved, run the skill to get a ready-to-code branch issue-153-retrieval-topology with delivery templates prepared, then implement and hand off to the delivery step. ## Quick Start Ask the assistant to start work on GitHub issue 153 so it syncs main, creates the feature branch, and scaffolds the delivery templates.

Frequently Asked Questions about forge-start

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

FAQPage Schema
How do I create a feature branch for a GitHub issue from latest main?

Fetch and fast-forward local main with git pull --ff-only, then create a branch named issue-<number>-<slug> where the slug derives from the issue title. The skill automates this sequence and stops if main has diverged instead of force-resetting.

How to auto-assign a GitHub issue to the current user with gh CLI?

Run gh issue edit <number> --add-assignee @me. The @me token resolves from the current gh authentication context, so no hardcoded username is needed, and the command is idempotent if the issue is already assigned.

What happens if local main has diverged from origin main?

The git pull --ff-only command fails when local main has diverged, and the skill reports the blocker and stops. It does not force-reset main, surfacing the situation to the user for manual resolution instead.

When should I run this branch setup step in a delivery workflow?

Run it after an implementation plan has been approved and before writing any code. It bridges planning and implementation by ensuring the branch is cut from fresh main and delivery templates exist before work begins.

Why avoid complex jq expressions when deriving a branch slug from an issue title?

Complex jq expressions with pipes or gsub contain characters that fail shell allow-list matching and trigger approval prompts. The slug transformation should be done in-context after fetching the title with a simple gh issue view query.