Files

T

naps62 181ee03cc2 feat(claude): add /work and /yolo Linear workflow skills

Replace the old /work command with two new skills backed by Linear:
- /work: proper flow (plan, PR, CI iteration, review loop)
- /yolo: fast flow (implement, push directly, done)

Both share common config via linear-common/COMMON.md and use
per-project .claude/linear.json for org, team, build commands, etc.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-10 10:38:35 +00:00

1.5 KiB

Raw Blame History

name, description, user-invocable, args

name

description

user-invocable

args

yolo

Pick a Linear task (or create one), implement in a worktree, push directly with minimal ceremony

true

name	description	required
input	A Linear issue ID (e.g. ERN-347), an ad-hoc task description, or omit to auto-pick next unblocked task	false

Yolo - Quick Ship Flow

Fast autonomous workflow: Linear issue -> worktree -> implementation -> push -> done. No PRs, no reviews.

First: Read ~/.claude/skills/linear-common/COMMON.md for shared setup instructions.

Workflow

1. Setup (from COMMON.md)

Load project config
Select task (from $ARGUMENTS)
Set up worktree
Gather context

2. Implement

Follow the implementation guidelines from COMMON.md. Move fast — this is yolo mode.

Skip formal planning. Read the issue, understand it, start coding.
Still write tests if the project has them, but don't block on edge cases.
Run the buildCommand if configured. If it fails, fix it. If a failure is minor and unrelated to your change, warn the user but keep going.

3. Ship

Push the branch: git push -u origin <branch>
If the work is complete and self-contained, merge to the default branch:
```
git checkout <defaultBranch>
git merge <branch> --no-edit
git push
git checkout <branch>
```
Only do this if the change is clearly ready. If unsure, just push the branch and let the user decide.
Move the Linear issue to "Done".
That's it. No PR, no review loop.

1.5 KiB Raw Blame History