<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jared Rhizor</title>
    <description>The latest articles on DEV Community by Jared Rhizor (@jrhizor).</description>
    <link>https://dev.to/jrhizor</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F995048%2F26ea3d3e-047f-43d8-b079-6868e046edf9.png</url>
      <title>DEV Community: Jared Rhizor</title>
      <link>https://dev.to/jrhizor</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jrhizor"/>
    <language>en</language>
    <item>
      <title>Open Source AEO / GEO</title>
      <dc:creator>Jared Rhizor</dc:creator>
      <pubDate>Tue, 02 Jun 2026 03:49:45 +0000</pubDate>
      <link>https://dev.to/jrhizor/open-source-aeo-geo-1m6b</link>
      <guid>https://dev.to/jrhizor/open-source-aeo-geo-1m6b</guid>
      <description>&lt;p&gt;I'm excited to announce &lt;a href="https://www.elmohq.com/?ref=devto" rel="noopener noreferrer"&gt;Elmo&lt;/a&gt;, an open source AEO / AIO / GEO tool that tracks AI visibility. It's the most popular, regularly maintained AI visibility tracker on GitHub.&lt;/p&gt;

&lt;p&gt;A lot of tools in this space are very expensive or have a lot of lock in. Really you just need to run prompts against LLMs, track mentions, and analyze citations. I'm also using it to improve the AI visibility for Elmo itself (although it's still early days).&lt;/p&gt;

&lt;p&gt;All you need to run is Docker and a web scraper API key (like BrightData) and OpenAI/Anthropic/Mistral/OpenRouter API key, and you're good to go.&lt;/p&gt;

&lt;p&gt;There's a lot coming soon (sentiment analysis, content simulations, etc) but it's already in use by a number of e-commerce and SaaS sites.&lt;/p&gt;

&lt;p&gt;Curious to hear what you think!&lt;/p&gt;

</description>
      <category>ai</category>
      <category>aeo</category>
      <category>analytics</category>
    </item>
    <item>
      <title>Track your GitHub workflow performance in every pull request</title>
      <dc:creator>Jared Rhizor</dc:creator>
      <pubDate>Fri, 23 Dec 2022 06:33:43 +0000</pubDate>
      <link>https://dev.to/jrhizor/track-your-github-workflow-performance-in-every-pull-request-6ak</link>
      <guid>https://dev.to/jrhizor/track-your-github-workflow-performance-in-every-pull-request-6ak</guid>
      <description>&lt;h2&gt;
  
  
  Tutorial
&lt;/h2&gt;

&lt;p&gt;You can view a chart of GitHub job runtimes in a PR comments in just two minutes!&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Install GitHub Application
&lt;/h3&gt;

&lt;p&gt;Go to the &lt;a href="https://github.com/apps/stoat-app/" rel="noopener noreferrer"&gt;Stoat GitHub application page&lt;/a&gt; and install the application for your repository.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Install CLI
&lt;/h3&gt;

&lt;p&gt;Requirements:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Node/NPM&lt;/li&gt;
&lt;li&gt;Mac/Linux&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To install the Stoat CLI, run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npm i -g stoat
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  3. Initialize Stoat
&lt;/h3&gt;

&lt;p&gt;To initialize a Stoat project within a Git repository, run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;stoat init
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The initialization command will create a configuration file for Stoat at &lt;code&gt;.stoat/config.yaml&lt;/code&gt; and will give you the option to add the Stoat GitHub action as the final step in all GitHub jobs. Say yes for every job you want to track job runtimes for. Merge these changes into your repo. &lt;/p&gt;

&lt;h3&gt;
  
  
  That's it!
&lt;/h3&gt;

&lt;p&gt;You will now see build runtimes tracked in your PRs! Here's what the build history looks like after multiple default branch builds and commits in a PR:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fstoat-dev--static.stoat.page%2Fscreenshot-graph.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fstoat-dev--static.stoat.page%2Fscreenshot-graph.png" alt="screenshot"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This type of graph will be posted in a PR comment and updated as new commits are pushed to the PR.&lt;/p&gt;

&lt;h3&gt;
  
  
  There's more!
&lt;/h3&gt;

&lt;p&gt;Stoat aims to turn pull request comments into developer dashboards. It already supports previews for build artifacts (including test coverage reports, documentation static sites, StorybookJS, and more).&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fstoat-dev--static.stoat.page%2Fscreenshot-readme.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fstoat-dev--static.stoat.page%2Fscreenshot-readme.png" alt="screenshot"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://docs.stoat.dev/" rel="noopener noreferrer"&gt;Check out the docs for more info »&lt;/a&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>ci</category>
      <category>programming</category>
      <category>stoat</category>
    </item>
  </channel>
</rss>
