bro
Restate the last assistant response in plain language, covering what happened, what it means, and what to do next. Use it when the user asks to explain that, say it in plain English, or eli5. With a topic after `/bro`, such as `/bro what is this ticket for`, explain that topic instead. Not for redoing the work or for ordinary questions without `/bro`.
- License 许可
- MIT
- 所属仓库
- sQVe/tau
- 最近更新
- 2026-11-13
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- bro
- description
- Restate the last assistant response in plain language, covering what happened, what it means, and what to do next. Use it when the user asks to explain that, say it in plain English, or eli5. With a topic after `/bro`, such as `/bro what is this ticket for`, explain that topic instead. Not for redoing the work or for ordinary questions without `/bro`.
03 SKILL.md 正文
Bro
When to use
Use this skill when the user did not understand the last assistant response and asks for it in plain
language, or runs /bro with a topic.
Hard rules
- Change nothing.
- Name real files, commands, and numbers instead of categories.
- Do not use jargon, tables, or raw tool output.
Without a topic
- If there is no earlier assistant response, say so, ask what to explain, and stop.
- Restate the last assistant response, not the request that started this skill.
- Write a few sentences: what happened, what it means, and what to do next.
- Explain the response. Do not redo it. Beyond loading this skill, make no tool calls, start no new investigation, and give no revised answer. If that response was wrong, fixing it is a new request.
- Report the same outcome that response reported. A failure stays a failure. Do not soften it into "mostly working" and do not turn a warning into a crisis.
- If that response asked a question or laid out a decision, restate the choice and what each option costs. Do not pick one. The decision is still the user's.
With a topic
- Write a few sentences that answer the topic.
- Use the conversation first. Read the named source, such as the ticket, only when facts are missing.
- Diagnose no new problem and plan no implementation.
- If the topic or its source is unclear, ask instead of guessing.
04 同仓库更多 Skills
benchmark-checklist
Check evidence before measuring performance or reporting a speedup, regression, or comparison.
worktree
Create or open a Git worktree for a ticket or task with Grove and open it as a herdr-app space. Use it when asked to create, add, start, or open a worktree, optionally followed by a handover.
update-branch
Rebase the current branch onto its base, resolve conflicts, and update the PR when asked. Use it for "rebase onto main", "fix conflicts", "the PR has conflicts", or when a rebase or merge stops on a conflict.
triage-findings
Verify review findings or comments the user asked you to act on, fix the supported ones in scope, and report each one as Fixed, Not worth changing, Incorrect, or Blocked. Use it for "triage these findings", "fix these review comments", or "act on the findings I approved". `code-review`, `pr`, and `start-slice` also start it after a review of the user's own work.
tracker
Write Linear tickets by Tau's rules. Pick the type and template, route it, search for duplicates, and use checked tools for ticket writes and the two allowed status changes. Use it for "file a bug", "create a ticket", or "add a follow-up ticket". It does not split designs or start slices.
tdd
Change behavior test-first with Tau's run_tests tool, then verify the affected tests and a mutation check. Use it when changing behavior. Covers the cycle and survivor handling, not test design.