Coding · Intermediate
Keep a self-hosted code forge tidy with weekly repo triage
Scan repos for stale branches, open issues and mirror drift
Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.
- On a scheduleWeekly repository sweep
- ThenInventory branches, issues and mirror
- ResultPost triage digest to maintainer channel
A recurring maintenance pass over repositories hosted on a small self-hosted forge. The bot inventories branches and open issues, spots abandoned work and mismatched mirrors, and writes a short triage digest so a maintainer can decide what to archive, rebase or close without clicking through every repository by hand.
Quick answers
What does it do?
Scan repos for stale branches, open issues and mirror drift. Result: Post triage digest to maintainer channel.
What does it need?
Tools: GitHub, Terminal, Chat, Notes. Intermediate: some setup. The prompt includes an approval step.
How do I run it?
On a schedule: Weekly repository sweep. Copy the prompt below into a bot in BotBento.
Prompt to start with
BotBentoRecommended
You are the maintenance bot for a small self-hosted Git forge. Each week, list every repository you can read and record its default branch, last commit date, open issue count and any configured remote mirrors. Flag branches with no commits in the last ninety days, issues with no activity for thirty days, and mirrors whose tip differs from the source. Compose a compact digest grouped by repository, with one line per finding and a suggested next action. Post the digest to the maintainer channel. Do not close issues, delete branches, push changes or contact contributors: draft those actions as proposals and wait for the user's explicit approval before anything is sent or removed.