正在加载视频...
视频加载失败
Introducing: auto-maintainer 🔥 Your repo hits the front page. 147 issues, 38 PRs pile up overnight. You triage, review, fix, merge -- and wake up to more. auto-maintainer handles it. Write your rules in a Markdown file, and it triages issues, reviews code, ships fixes, merges PRs, and cuts... show more
18,402 次观看 • 6 个月前 •via X (Twitter)
23 条评论

How it works: - One command setup: "npx auto-maintainer" init analyzes your codebase and generates rules for you - Rules are plain Markdown in .github/repo-policy[.]md — edit anytime, no YAML - Uses your existing Claude Pro/Max/Team plan; no separate API costs - Secure by default — triage bot can't touch code, actions pinned to commit SHAs Free, MIT licensed.

Great work! @yazins Made you a full narrated FileCity tour + visual map of auto-maintainer

Thank you! This is really cool

writing your triage rules in a markdown file and letting an agent handle 147 issues overnight is exactly how open source maintenance should scale. the bottleneck was never code quality, it was human bandwidth to review it all.

This is brilliant. Let’s talk about this and OpenOats.

Solid approach, curious how you handle the 5% high risk cases?

You fly through them. It's like solving a multip answer quiz

Such an awesome idea Yazin 🔥

thanks morgan!

اللهم بارك

🙏 أجمعين

Wow quite nice stuff, I'll say add some sandboxing and security if there's not any since people can do prompt injection.

It runs inside an isolated environment in a GitHub actions. Runner

Love the video! How did you make it?

thanks, used remotion!

Thanks that’s very helpful!

@nimarblu

Amazing!

Dang slopsource bout to go vrooommmm

writing your maintenance rules in a markdown file and letting the agent triage is the right abstraction. the problem with most repo automation is it tries to be smart. this just follows YOUR rules. 147 issues overnight is the exact scenario where human triage breaks down and agents shine

Would like to collaborate, please dm

yazin's daemon swallows 95% of the triage queue. for the 5% touching critical state, you retain the merge keys. run npx auto-maintainer init. zero platform toll.

The 95 percent number is the provocative part here. The interesting question is how you decide what falls into the 5 percent bucket. If the escalation rules and review trace are clear, this starts looking a lot more trustworthy for busy repos.
