Baton approve

Work-item lifecycle over a board — backend-agnostic CLI + Claude Code skills (GitHub Projects, Plane, ...)

Install

npx -y skills add SOSkr/baton --skill baton-approve

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Approve a triaged work-item: advance it to the board's approved stage. Use when the user says "approve X", "aprobar idea", or confirms approval after triage.

SKILL.md

1.2 KB, 257 tokens by cl100k_base, as published. Nobody here has run it

baton approve

Approve a reviewed item — moves it to the "approve" stage (config alias, default Approved). No branches here (that's baton-start).

Workflow

Verify the item is in the pre-approval stage:

baton show <id>          # check its stage
baton stages             # the board's stages, in order

Confirm priority with the user (drives implementation order); adjust the priority label if needed:
```
baton labels <id> --remove priority:medium --add priority:high
```
Approve (advance to the approved stage):
```
baton approve <id>
```
approve resolves the stage from config.stages.approve (default Approved). For a non-standard board, use baton advance <id> --to "<Stage Name>".

Notes

State = board stage, not labels. The approved backlog = items in the approved stage, ordered by priority label (baton list --stage Approved).
Implementation starts with baton-start.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.