loncadev

baron

Drive work tracking (issues) and source control (pull requests) through Baron's provider-agnostic ports. Use when the user asks to create/transition/comment/link/query issues, open branches or pull requests, or run a Baron recipe — across Azure DevOps, GitHub, or whatever the repo's .baron/policy.json binds.

task-list

List work items with Baron, filtered by role, type, or assignee — "my in-progress work", "open bugs", "what's in review". Roles, not vendor states, so the same query works on any provider Baron binds. Use when the user asks to list/show/find work items.

task-move

Move a work item to a workflow role with Baron — guarding backward/reopen moves behind a required one-line reason (posted on the item first). Use when the user asks to change a task's state/column, send it back, reopen it, block/unblock it, or advance it. Roles, not vendor columns — works on any provider Baron binds.

task-new

Create a NEW work item with Baron — reach a well-specified item first (grill for the missing detail when the input is thin), infer the type role (task/bug/story), resolve the right parent, then create it. Use when the user describes new work to record ("we need...", "bug:", "add a task for..."). Starting work on it afterwards is task-start.

task-start

Start work on an EXISTING work item with Baron — load it, cut its canonical branch, move it to in_progress, and sync the local checkout. Use when the user says to start/pick up/resume a known task, bug, or story (by id, key, or URL). To create a new item first, use task-new.

task-sync

Sweep in-flight work items for drift between their workflow role and their branch's PR reality — the classic "the PR merged but the card is still in progress" — and batch-fix it with Baron. Use when the user asks to sync/reconcile the board, tidy stale cards, or "what's still in progress but actually done?".

DevOps & Infrastructure Listed

run-recipe

Run any Baron recipe by name as ONE deterministic, rule-enforced workflow. Use when the user names a recipe to run (including a project recipe under .baron/recipes) and no dedicated skill covers it.

task-finish

Finish a work-item branch with Baron — push it, open (or find) the draft pull request, and post the PR link on the item. Use when the user says the work is done / ready for review / open a PR. The item's role does NOT move here — it moves when the PR merges.

task-land

Land a work item's pull request with Baron — take it out of draft and merge it. Use when the user says merge it / land it / birleştir / it's approved, ship this PR. Do NOT shell out to `gh` or `az` for this; Baron owns the provider call, including the parts that have no REST route.

ship

Ship a change with Baron — open a draft PR, move the issue to in_review, trigger its CI pipeline, and notify the team, as ONE deterministic single-pane workflow across scm + issues + ci + notify. Use when the user says "ship it", "ship this change", or asks to PR + run CI + notify together.