Start Issue

If you're managing GitHub issues through Marshroom's cart system, this automates the tedious setup when you start work. It finds the issue in your local state file, checks out a properly named branch, pulls latest from main, and critically, updates the issue status to running. The skill is opinionated about branch naming (Feature/#N or HotFix/#N) and won't let you proceed if the state.json update fails, which is the right call since Marshroom depends on that file for tracking. It injects the full issue body as context and optionally kicks into plan mode. Saves you from manually syncing state between your issue tracker and git branches.

skills.sh installs: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add vkehfdl1/marshroom --skill start-issue --agent claude-code

Installs into .claude/skills of the current project.

Files

Start working on a Marshroom cart issue in the current repository.

Critical Requirements

state.json update is MANDATORY. After creating the branch, you MUST update the issue status to running in ${MARSHROOM_STATE:-~/.config/marshroom/state.json}. If this fails, stop and report the error — do NOT silently continue.
Use marsh start if available; otherwise fall back to direct jq atomic write (see step 10).