yunidbauza
@yunidbauza
Public Skills
work-on
by yunidbauza
Use when a Hive session starts work on a Jira ticket. "work on HIVE-123", "start ABC-42", the next story in an Epic, or a session opened from the Work tab. Reads the ticket, reconciles it against the code as it is today, gets the go-ahead once, brainstorms and plans in the terminal, then hands the plan to the builder agent or executes it inline. Use goal-on when there is no ticket.
plan
by yunidbauza
Use when a spec or an approved design exists and the work is more than one step, before touching code. Writes the plan a builder run or an inline execute run follows task by task. Tasks are sized in builder minutes (about five per TDD task), each marked risk-bearing or not, and a ticket over thirteen points becomes more than one PR.
ship
by yunidbauza
The PR endgame, run by the shipper agent on every wake. Drives a draft PR to merge one stage at a time: self review through the reviewer agent, mark ready, CI, findings through fixer, approval or the auto-merge fence, merge-pr, Jira Done. A session hands a PR over with one ledger_ask to shipper; in a terminal this skill only explains how.
pr-review
by yunidbauza
Multi-agent PR review. Posts one review on a pull request, approving only when clean, or with --self reviews your branch's whole diff and returns the findings. Re-checks earlier findings and the Jira ticket's scope.
review-pr-findings
by yunidbauza
Use when a PR has feedback to work through: reviewer comments, a review's summary (an approval's included), bot findings, a red check, or the self review's findings. Assesses every finding adversarially, fixes the valid ones behind a test, replies to every finding, pushes once per round, and repeats until green with every thread resolved and every finding answered. Run by the fixer agent; also runs in a session on request.
merge-pr
by yunidbauza
Use when a PR is approved and green and it is time to merge it, "merge the PR", "squash and merge", or the shipper's merge stage. Re-checks every merge blocker in one reading immediately before merging, squash merges against that exact head, tears down the worktree and the branch, pulls the default branch, and moves the Jira ticket to Done only when the key is confirmed.
goal-on
by yunidbauza
Use when a request is vague, broad or ad hoc and has no Jira ticket. "figure out X and do it", "sort out this mess", "look into Y and fix whatever's wrong". Turns the prompt into a Task/Scope/Constraints/Outcome brief, gets approval once, then holds the session to the Outcome with a Stop hook until the evidence exists. Use work-on when a ticket exists.
execute
by yunidbauza
Use when a written plan exists and it is time to build it. Runs the plan task by task with a commit each, inline by default, and escalates to subagents only when the plan spans two or more subsystems with no shared test harness and touches a risk surface. Used by the builder agent and by work-on --inline and goal-on.
worktree
by yunidbauza
Use when starting feature work that must not touch the shared checkout, before any edit. A builder or fixer run, an isolation-guarded session, or any work that needs its own branch off a fresh default branch. Reuses a linked worktree already on the branch or creates an isolated one, verifies the baseline, and says where it is.
spec-deviation
by yunidbauza
Use when an implementation has deviated from its Jira ticket: a design decision changed mid-work, the plan diverged from the ticket, or the user says "update the ticket with the deviation", "add UPDATED SPECS", or "update the downstream tickets". Writes the deviation into the PR body, appends UPDATED SPECS to the ticket, and proposes edits to the downstream tickets for confirmation before writing them.
debug
by yunidbauza
Use on any bug, failing test, build failure or unexpected behaviour, before proposing a fix. Root cause first, one hypothesis at a time, and the fix lands behind the test that reproduces the bug. Especially when a quick fix seems obvious or the last fix did not work.
verify
by yunidbauza
Use before claiming any work complete, fixed or passing, and before pushing, opening a PR or reporting done to the ledger. Runs the repository's own gates, drives a UI change in a real browser, and records the output as evidence. No claim without fresh output in the same message.
brainstorm
by yunidbauza
Use before any creative work in a Hive session, creating features, components or changing behaviour, and before writing a plan. Classifies the work as a spike, a bounded change or architectural, explores intent, and produces a spec for the architectural path. Invoked by work-on and goal-on; never dispatched to an agent.
tdd
by yunidbauza
Use when implementing any feature or bug fix, before writing production code, and when a PR finding asks for a behaviour change. No production code without a failing test first; code written before its test is deleted, not adapted.