Skip to content
Back to search

orca-bots

Ready-to-install Orca bots for engineering teams: a pull request reviewer that verifies by running the code, and a garbage collector that removes useless comments and dead code in small PRs

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mariano-aguero--orca-bots/badge.svg)](/listings/mariano-aguero--orca-bots)

HTML

<a href="/listings/mariano-aguero--orca-bots"><img src="/api/listings/mariano-aguero--orca-bots/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Every bot does its GitHub work with `gh`, so it needs `gh` installed and signed in as you. The Orca GitHub app is optional: with it, GitHub events wake the bots; without it, they run on a schedule and find the work with `gh`. Use one or the other for a bot, not both.

1. Create the bot in Orca. 2. Copy its `SOUL.md` and its skill into `~/.orca/bots/<bot>/`, as its README shows. 3. Add the event or schedule that wakes it.

Every bot starts in a mode where nothing reaches your repos without you, and its README says how to widen that.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 53 lines
  1. # orca-bots
  2. [![Orca](https://img.shields.io/badge/built%20for-Orca-1f6feb)](https://github.com/stablyai/orca)
  3. [![Bots](https://img.shields.io/badge/bots-7-8250df)](#bots)
  4. [![Last commit](https://img.shields.io/github/last-commit/mariano-aguero/orca-bots)](https://github.com/mariano-aguero/orca-bots/commits/main)
  5. [![License: MIT](https://img.shields.io/github/license/mariano-aguero/orca-bots?color=green)](LICENSE)
  6. [![Stars](https://img.shields.io/github/stars/mariano-aguero/orca-bots?style=flat)](https://github.com/mariano-aguero/orca-bots/stargazers)
  7. Bots for [Orca](https://github.com/stablyai/orca), ready to install. Each one does a single job for an engineering team, works as you through `gh` and your trackers, and keeps a person in charge of anything that reaches the main branch.
  8. ## Bots
  9. | Bot | Starts on | What it does | Writes |
  10. |---|---|---|---|
  11. | [Pull request reviewer](pr-reviewer/) | A review request, a mention or new commits | Checks the PR against its task, verifies it by running the code, and drafts validated inline comments with suggested fixes | Nothing until you allow it |
  12. | [Garbage collector](garbage-collector/) | A schedule | Removes useless comments and proven dead code and tests, one small PR per app | PRs against an integration branch, never merged |
  13. | [Daily standup notes](standup-notes/) | A weekday schedule | Writes Yesterday / Today / Blockers from your Orca workspaces, pull requests and Linear issues | Nothing |
  14. | [PR shepherd](pr-shepherd/) | A review, comment, failing check or merge on your own PR | Sorts review threads, prepares fixes with tests in its own clone, diagnoses failing checks, says when a PR is ready | Local commits until you allow pushes |
  15. | [Chief of staff](chief-of-staff/) | A weekday schedule, morning and evening | One plan from your issues, reviews, PRs, meetings and the other bots, and hands approved work to the right bot | Hand-offs and issues you approve |
  16. | [Eng lead](eng-lead/) | A hand-off | Plans an issue, waits for your OK, runs a writer and a verifier worker | Draft PRs |
  17. | [Ops watch](ops-watch/) | A schedule and failed checks | Reports new production and staging problems with their likely cause, and drafts the issue | Issues you approve |
  18. ## Layout
  19. Every bot folder has the same shape:
  20. ```text
  21. <bot>/
  22. SOUL.md who the bot is, what wakes it, what it reports, what it may never do
  23. skills/<name>/ the procedure, as a skill the bot runs
  24. README.md what it does and how to install it
  25. examples/ automation prompts to copy, when the bot needs settings
  26. ```
  27. The soul stays short and stable. The procedure lives in the skill, so it can improve without touching the bot's identity or its limits.
  28. ## Tools
  29. - `tools/gh-changed.sh`: a precheck for scheduled automations. It runs a read-only command and lets the run start only when the output changed, so a bot that polls GitHub with `gh` costs nothing when there is nothing new.
  30. ## Install
  31. Every bot does its GitHub work with `gh`, so it needs `gh` installed and signed in as you. The Orca GitHub app is optional: with it, GitHub events wake the bots; without it, they run on a schedule and find the work with `gh`. Use one or the other for a bot, not both.
  32. 1. Create the bot in Orca.
  33. 2. Copy its `SOUL.md` and its skill into `~/.orca/bots/<bot>/`, as its README shows.
  34. 3. Add the event or schedule that wakes it.
  35. Every bot starts in a mode where nothing reaches your repos without you, and its README says how to widen that.
  36. ## License
  37. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.