smarzban
- 18 skills
- 0 followers
- yesterday last updated
- ▌ Triage · smarzban bundleCheck an issue or a pull request that came from outside before anyone acts on it. For a bug report, reproduce it in the real app. For a feature request, check it against what the project is for. For a pull request, read what the diff really does. Ends with a verdict, a reply drafted for the owner, and for a reproduced bug a fix taken through `deliver` to a stop, with a before and an after set up for the owner to test. Use for "triage issue 12", "triage this PR", "check this bug report", "is this feature request worth doing", "sweep the new issues". Not for a task the owner wrote; that is `deliver`.
- ▌ Correct · smarzban bundleTurn a mistake that agents keep making in a repo into a check that fails, so the next agent cannot make it. Tries a design change first, then a type, then a lint, then a test, and writes a rule only as a last resort. Use for "correct this so it can't happen again", "agents keep doing X", "make this mistake impossible", "enforce this rule". Not for a one-off fix or a typo, and not for a finding inside a pull request that is still under review.
- ▌ Deliver · smarzban bundleTake one task from agreed to proven. State what done means, build, prove it in the running app, get it reviewed, open the pull request and get its checks green, then stop for the owner or merge when the owner said to. Use for "deliver this", "deliver T12", "deliver this and send it", "full send", "stop at the gate", "babysit this PR", "get this PR green", "file the PR and see it through". Not for reviewing someone else's pull request or for planning work.
- ▌ Handoff · smarzban bundleWrite or pick up HANDOFF.md, the resume note that lets a new session, an agent in a different harness, or a coordinator continue a branch's work cold. Use when asked to "write a handoff", "hand off", "save state for a new session", "pick up where we left off", "resume this branch", or "what is each worktree doing", and when starting work in a worktree that contains HANDOFF.md.
- ▌ Release · smarzban bundleCut a release of a project. Find the repo's own release steps, write the changelog section from a short template with thanks to contributors, bump every file that holds the version, open the release pull request, then tag and publish the way that repo does (a tag, a GitHub release, an npm or other registry publish through its workflow) and check the result. Use for "cut a release", "release this", "release v1.2.0", "make a release", "prepare the release", "write the changelog", "tag a release", "publish to npm". Not for merging a pull request ("send it" is `deliver`), and not for creating a release workflow.
- ▌ Repo Setup · smarzban bundleSet up or audit a repo's working baseline for people and agents. Public AGENTS.md plus a gitignored AGENTS.local.md, ignore rules, one verify command that CI also runs, and a worktree setup script. Migrates an existing CLAUDE.md without losing a line. Use for "set up this repo for agents", "repo setup", "bootstrap the repo", "add AGENTS.md", "migrate CLAUDE.md to AGENTS.md". Not for installing dependencies or getting a project to run locally.
- ▌ Coordinator · smarzban bundleRun several builder agents for the owner. Plan the work into tasks, brief each builder, start it in its own worktree, review its pull request, test the result, then hand it to the owner or merge it when the owner said to. Use for "coordinate this", "run builders on these tasks", "coordinate the board", "put builders on the plan", "take charge of the builders while I'm away". Not for one agent doing one task or working a list alone; that is `deliver`.
- ▌ Writing Docs · smarzban bundleWrite, audit or update a project's docs from its source code. User docs (quickstart, install, configuration, a page per feature) and maintainer docs (architecture, data model, invariants), as plain Markdown or for a docs framework such as Starlight or MkDocs. Use for "write the docs", "document this repo", "user docs", "user guide", "docs site", "website docs", "architecture docs", "audit the docs", "update the docs", "the docs are out of date". Not for creating or hosting a docs site.
- ▌ Comment Audit · smarzban bundleAudit the code comments in a repo and remove the ones that add nothing, fix the ones that are wrong, and turn the ones that point at a real problem into tasks. Keeps a comment only when it tells a reader something true that the code cannot. Use for "audit the comments", "clean up the comments", "remove useless comments", "prune the comments", "the comments are noise", "check the comments are still true". Not for writing docs or adding comments, not for comments on a pull request or an issue, and not for stopping a kind of comment from coming back; that is `correct`.
- ▌ Shared Skills · smarzbanAdd, edit or remove a skill in the user's shared agent-skills repo, the single source of skills for Claude Code, Codex, Cursor, Pi and Grok. Use when asked to "create a skill", "save this as a skill", "add this to my skills", "update the X skill" or "make this available to all my agents".
- ▌ Writing Readmes · smarzban bundleWrite, overhaul or review a repo's front-door README.md. The first screen says what the project is and who it is for, the quickstart is proven by a cold run, and reference material moves to docs. Use for "write the README", "fix the README", "review the README", "the readme isn't clear", or a README that has grown into a docs dump.
- ▌ Publishing A Repo · smarzban bundleCheck a private repo before its owner makes it public, and report what to fix. Covers secrets in git history, private names and links, licences, security policy, CI exposure to forks, discovery metadata, and a quickstart run from a clean clone. Run only when the user explicitly asks for a pre-publication check, for example "publishing-a-repo", "prepare this repo to go public", "pre-publish check".
- ▌ Verification Skill · smarzban bundleCreate, adopt or maintain a project's own verify-<app> skill, the scripted way for any agent to launch the real app, drive a feature the way a user does, and capture proof. Use for "create a verification skill", "make a control skill for this repo", "set up verification for this app", "move the verify skill", "maintain the verification skill", "audit the verify skill". Not for running a verification; the generated skill does that.
- ▌ Herdr File Viewer · smarzbanOpen a known repository file, source line, or source range in a Herdr Files pane for the user to inspect.
- ▌ Tsk CLI · smarzbanWork 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.
- ▌ Spawn · smarzbanFan 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.
- ▌ Review Panel · smarzbanUse 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.
- ▌ Pi Review · smarzbanLaunch 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.