<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: cleverdash</title><link>https://news.ycombinator.com/user?id=cleverdash</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 14 Apr 2026 16:36:53 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=cleverdash" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by cleverdash in "Show HN: SEOLint – MCP server that lets Claude scan any site for SEO issues"]]></title><description><![CDATA[
<p><a href="https://youtu.be/mzff8hWgsuA" rel="nofollow">https://youtu.be/mzff8hWgsuA</a></p>
]]></description><pubDate>Tue, 14 Apr 2026 11:59:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=47764469</link><dc:creator>cleverdash</dc:creator><comments>https://news.ycombinator.com/item?id=47764469</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47764469</guid></item><item><title><![CDATA[Show HN: SEOLint – MCP server that lets Claude scan any site for SEO issues]]></title><description><![CDATA[
<p>Article URL: <a href="https://seolint.dev">https://seolint.dev</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47764468">https://news.ycombinator.com/item?id=47764468</a></p>
<p>Points: 1</p>
<p># Comments: 1</p>
]]></description><pubDate>Tue, 14 Apr 2026 11:59:42 +0000</pubDate><link>https://seolint.dev</link><dc:creator>cleverdash</dc:creator><comments>https://news.ycombinator.com/item?id=47764468</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47764468</guid></item><item><title><![CDATA[New comment by cleverdash in "GitHub Stacked PRs"]]></title><description><![CDATA[
<p>As a solo dev I rarely need stacked PRs, but the underlying problem, keeping PRs small and reviewable, is real even when you're your own reviewer. I've found that forcing myself to break work into small branches before I start (rather than retroactively splitting a giant branch) is the actual discipline. The tooling just makes it less painful when you don't.<p>Curious whether this changes anything for the AI-assisted workflow. Right now I let Claude Code work on a feature branch and it naturally produces one big diff. Stacked PRs could be interesting if agents learned to split their own work into logical chunks.</p>
]]></description><pubDate>Mon, 13 Apr 2026 20:57:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=47757721</link><dc:creator>cleverdash</dc:creator><comments>https://news.ycombinator.com/item?id=47757721</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47757721</guid></item><item><title><![CDATA[New comment by cleverdash in "Building a CLI for all of Cloudflare"]]></title><description><![CDATA[
<p>The trend of CLI-first design because AI agents need it is interesting. We ended up in the same place building developer tools, the CLI and API came first because that's what agents actually consume. The dashboard came after.<p>The cf permissions check idea from the top comment is great. One thing I've found is that agents are surprisingly good at using CLIs but terrible at diagnosing why a command failed. Clear error messages with the exact fix ("missing scope X, run cf token add --scope X") matter way more for agent usability than the happy path.</p>
]]></description><pubDate>Mon, 13 Apr 2026 20:55:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=47757697</link><dc:creator>cleverdash</dc:creator><comments>https://news.ycombinator.com/item?id=47757697</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47757697</guid></item></channel></rss>