<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Source on René Zander | AI Automation Consultant</title><link>https://renezander.com/tags/open-source/</link><description>Recent content in Open-Source on René Zander | AI Automation Consultant</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 09 Apr 2026 14:00:00 +0200</lastBuildDate><atom:link href="https://renezander.com/tags/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Issue Management AI: Build Claude-Powered Triage That Works</title><link>https://renezander.com/blog/github-issue-management-ai/</link><pubDate>Thu, 09 Apr 2026 14:00:00 +0200</pubDate><guid>https://renezander.com/blog/github-issue-management-ai/</guid><description>&lt;p>Maintainers do not ship software on Tuesday mornings. They triage. They read a new issue, check whether it is a duplicate of something filed three weeks ago, decide whether it is a bug or a question, pick a priority, add two or three labels, and sometimes write a polite comment asking for a repro. Then they do it again for the next issue in the queue. The job is pure admin, and on any active repo it eats real hours every week.&lt;/p></description></item><item><title>AI GitHub Issue Triage with FixClaw: Human in the Loop</title><link>https://renezander.com/guides/fixclaw-ai-github-triage/</link><pubDate>Sat, 28 Mar 2026 14:00:00 +0100</pubDate><guid>https://renezander.com/guides/fixclaw-ai-github-triage/</guid><description>&lt;p>Open source maintainers do not burn out from writing code. They burn out from the inbox. A hundred open issues, half of them duplicates, a third missing a stack trace, and somewhere in there the one real bug that will bite a paying user tomorrow. FixClaw is an &lt;strong>AI GitHub issue triage&lt;/strong> tool built to take that load off without taking the keys away from you.&lt;/p>
&lt;p>This is a product landing page, not a tutorial. If you want to build your own triage system from scratch, skip to the Related Reading at the bottom. If you want &lt;strong>github issue automation&lt;/strong> that reads like a helpful junior maintainer and waits for your approval before posting anything, keep reading.&lt;/p></description></item></channel></rss>