logbook

Plugin logbook from marketplace logbook in groovy-os/logbook-plugin. Commands read from the repo's manifest — 22 days ago.

Skills (10)

• add

  Turns a rough idea, or an issue discovered mid-work, into a meaty self-contained build brief on the logbook board — problem, size/risk tier, acceptance criteria, affected modules and files, test plan, doc-update list. Use whenever work is about to be filed: any time create_item, create_items, or upd

• explore

  Investigates a logbook item before it gets built — does the same problem exist elsewhere in the codebase (other pages, modules, endpoints, similar code paths), and is the item's proposed fix still accurate against the current code? Treats the item's problem as a hypothesis, researches the blast radi

• jot

  Writes a note on the user's private notepad — the personal column on the logbook board, not a note attached to a log. Use for a thought with no home yet: a hunch, a follow-up to look at later, something noticed in passing while doing something else. Invoke when the user says "jot that down", "note t

• loop

  Runs a batch of logbook items through the full engineering gauntlet — triage, conflict-clustering, build, fresh-eyes review, a capped fix loop, and a merge-order plan — until every item is a clean, conflict-mapped PR awaiting human review.

• merge

  Plans and executes the merge of a batch of READY logbook pull requests into the base branch without conflict or multi-head cascades — diffs each PR's files, builds a collision graph, linearizes the migration chain so the batch produces one head, produces a conflict-aware merge order, and (optionally

• plan

  Plans the optimal build path through the open logbook backlog — clusters open items (assigned or unassigned) into logical batches by file-collision, module affinity, and dependency order ("if you're doing LOG-123, do 122 and 124 in the same pass"), sequences the batches, and emits paste-ready /logbo

• recap

  Reports what shipped recently — logs closed in the last few days, each with its resolution and the pull requests it links to. Use for a standup, a weekly summary, a changelog draft, or when the user asks "what did we get done this week", "what shipped", "what closed recently", "recap the week", or t

• review

  Reviews a logbook item's pull request with fresh eyes — reads the item's spec, checks the diff against the acceptance criteria and the repo's own gates, and posts one structured PR comment carrying a READY FOR HUMAN REVIEW or CHANGES REQUESTED verdict. Use when logbook:loop dispatches a review round

• sweep

  Runs an orchestrated cleanup audit of the logbook backlog — finds items that are already done (merged-but-uncrossed), obsolete, duplicated, or stale-briefed, closes them with evidence-backed resolutions, and produces a bill of work for the human. Runs as a director/worker system with model tiering a

• ux

  Specs the UX/UI depth of a front-end logbook item BEFORE it is built — inverts a thin, endpoint-shaped brief into a real product surface (job-to-be-done, flows, every state, data hierarchy, affordances, real microcopy) and attaches that spec to the item as `ux-spec.md` so the build has depth instead

Similar plugins