smarzban

@smarzban source repo

5 skills
0 followers
18 hours ago last updated

▌
Herdr File Viewer · smarzban
Open a known repository file, source line, or source range in a Herdr Files pane for the user to inspect.

0
installs
▌
Tsk CLI · smarzban
Work the user's tsk task board from the command line. Use when asked to add, update, edit, start, block, finish, archive, or restore a task on the board (or "tsk", "the tsk board", "the desk"), to add or tick steps, to answer "what's on the board", "what's next", "what's on deck", "what needs me", or to refine a task ("refine T12", "let's discuss T12", "what's missing from T12", "improve / rewrite this task"). Always `tsk add|list|status|edit|steps|archive|trash`, never the TUI.

0
installs
▌
Spawn · smarzban
Fan out a confirmed research/implementation brief to named Pi agents in parallel via pi-spawn tools. Use when the user asks to spawn agents, run the agents on this, compare models on a question, get the agents to investigate, or otherwise parallelize the same brief across configured named agents.

0
installs
▌
Review Panel · smarzban
Use when asked to review a PR or diff, or audit a repository. Call review_panel with review, audit, diagnose, verify, or comment. Never call it with {}. Judge findings and keep repair in the harness.

0
installs
▌
Pi Review · smarzban
Launch Pi and have it run Review panel on a PR or local change. Pi only reviews and re-reviews. You or the builder implement agreed findings, then ask the same Pi session to verify. Use when asked to review a PR, review this diff, run review panel, or /pi-review. In Herdr (HERDR_ENV=1) you MUST open a sibling pane and start Pi there. Do not call review_panel yourself.

0
installs

5 published skills