start-issue — Claude Code skill: what it does, how to install
Pulls a Marshroom issue into your workspace, spins up a fresh Git branch, imports issue details, and marks the task as running.
npx skills add vkehfdl1/Marshroom --skill start-issue -a claude-codeWhat start-issue does
This skill connects your active repository to the Marshroom task queue. It inspects ${MARSHROOM_STATE:-~/.config/marshroom/state.json}, reads the Git origin via git remote get-url origin, and filters issues assigned to the matching owner/repo.
Before switching branches, it pulls the latest commits from main. Then it generates a Feature/#N or HotFix/#N branch and marks the issue status as running. For the update, it invokes marsh start or falls back to an atomic jq write. Without marsh or jq, the status update fails and halts the entire sequence.
Once the branch is ready, the skill prints the contents of issueBody under an issue header so your agent has full context. Finally, it asks for your permission to begin task planning in /plan mode.
What it helps with
- prepare a clean Git branch tied to an issue number
- inject ticket details directly into the coding agent context
- track task progress by updating Marshroom status to running
- match pending cart issues to the active repository automatically
Example prompts for the agent
- Start working on issue 15 with start-issue
- Pick the next Marshroom ticket and set up the branch
- Find matching cart issues for this repo and start working
How to install start-issue
1Skills CLI (Vercel)
npx skills add vkehfdl1/Marshroom --skill start-issue -a claude-code2Manually: put the files in place
~/.claude/skills/start-issue/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/start-issue/
1Skills CLI (Vercel)
npx skills add vkehfdl1/Marshroom --skill start-issue -a codex2Manually: put the files in place
.agents/skills/start-issue/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vkehfdl1/Marshroom --skill start-issue -a cursor2Manually: put the files in place
.cursor/skills/start-issue/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vkehfdl1/Marshroom start-issue2Manually: put the files in place
.github/skills/start-issue/SKILL.md1Skills CLI (Vercel)
npx skills add vkehfdl1/Marshroom --skill start-issue -a gemini-cli2Platform CLI
gemini skills install https://github.com/vkehfdl1/Marshroom --path marshroom-skills/skills/start-issueManually: put the files in place
.devin/skills/start-issue/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vkehfdl1/Marshroom --skill start-issue -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about start-issue
How do I install start-issue in Claude Code?
Run npx skills add vkehfdl1/Marshroom --skill start-issue -a claude-code in your terminal, or place the skill file at ~/.claude/skills/start-issue/SKILL.md.
What does the start-issue skill do?
It pulls main, checks out a new branch named Feature/#N or HotFix/#N, updates the issue status in Marshroom state, and displays the issue body for context.
What tools are needed for state updates?
It looks for the marsh binary in your PATH. If missing, it requires jq to execute an atomic update on ${MARSHROOM_STATE:-~/.config/marshroom/state.json}.
