Updated today
by escoffier-labs
brigade
Run coding agents anywhere and keep one record of the work, with tools and memory in sync across your harnesses. Local files, no daemon.
80 GitHub stars (80)
| Period | New stars |
|---|---|
| Oct 22 | 0 |
| Oct 23 | +1 |
- 10 skills (10 skills found in its SKILL.md files)
- 9 forks (9 forks)
- Today last update (Last updated today)
Install
Skills CLI
npx skills add escoffier-labs/brigade
Asks which skills and agents to install. Just one: npx skills add escoffier-labs/brigade --skill bug-hunt — add -g for every project.
Claude Code
git clone https://github.com/escoffier-labs/brigadecp -r "brigade/registry/skills/bug-hunt" ~/.claude/skills/
Copies the bug-hunt skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add escoffier-labs/brigade
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
bug-hunt
Use when asked to find bugs, hunt for correctness issues, sweep a codebase for defects, or verify a repo behaves as intended. Not for style or architecture review; this is defect-finding only.
registry/skills/bug-hunt/SKILL.md on GitHub (opens in a new tab) -
check
Use when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.
registry/skills/check/SKILL.md on GitHub (opens in a new tab) -
latent-premises
Use when reviewing a diff or module for hidden assumptions - things the code takes for granted that nothing guarantees - or when asked "what could break this later", "what does this assume", or to harden code that works today. Complements bug-hunt: bug-hunt finds defects with triggers today; this finds the ones waiting for tomorrow.
registry/skills/latent-premises/SKILL.md on GitHub (opens in a new tab) -
reduce
Use when asked to simplify, clean up, tidy, or refactor code for clarity without changing what it does, or when the user says "simplify this", "clean this up", "make it readable", "reduce the complexity", or "tidy this". Behavior-preserving only; not a bug or security audit (use bug-hunt or security-sweep for those).
registry/skills/reduce/SKILL.md on GitHub (opens in a new tab) -
refire
Use when anything misbehaves - a failing test, a production bug, a build break, flaky or unexpected behavior - before proposing or attempting any fix. Especially under pressure ("CI is blocking everyone", "just get it green") and after a previous fix didn't hold.
registry/skills/refire/SKILL.md on GitHub (opens in a new tab) -
retry-safety
Use when a diff carries side effects - database writes, migrations, file mutations, network calls, payments, queue messages - to check whether running it twice is safe. Also when reviewing retry logic, crash recovery, or anything a scheduler, queue, or impatient caller might re-run. Silent when the diff touches no side-effecting surface.
registry/skills/retry-safety/SKILL.md on GitHub (opens in a new tab) -
taste
Use when implementing any feature, bugfix, or behavior change, before writing the implementation code. Especially use under pressure - production is down, "just make it work", "quick fix" - which is when it gets skipped.
registry/skills/taste/SKILL.md on GitHub (opens in a new tab) -
verify-brigade
Prove a Brigade change works by driving the real `brigade` CLI against a throwaway temp target, then capture receipts as evidence. Use when you changed anything under src/brigade/ and need proof beyond pytest - init/doctor wiring, work-verify receipts, Grok Bot connector packs, feed manifests, handoff lint. Also use before claiming a CLI behavior in a PR body, handoff, or job report.
registry/skills/verify-brigade/SKILL.md on GitHub (opens in a new tab) -
brigade-work
Use at the start of any work session and whenever you verify a change in a Brigade-wired repo or workspace - routes work through Brigade so verification, outcomes, evidence export, and handoffs are captured (verify with capture → outcome from run → evidence brief next time) instead of leaving Brigade installed-but-dormant. Triggers on starting a task, running tests/checks, or finishing a session.
plugins/brigade/skills/brigade-work/SKILL.md on GitHub (opens in a new tab) -
enforce
Use when the user asks to turn on Brigade's full work loop (verification capture, raw-check blocking, and the handoff-before-stop gate) in the current repository.
plugins/brigade/skills/enforce/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.