<?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: jnsahaj</title>
    <description>The latest articles on DEV Community by jnsahaj (@sahajjj).</description>
    <link>https://dev.to/sahajjj</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%2F850197%2F593c793b-e754-4ad2-974a-3863924a3e9e.png</url>
      <title>DEV Community: jnsahaj</title>
      <link>https://dev.to/sahajjj</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sahajjj"/>
    <language>en</language>
    <item>
      <title>Free Insights for any Bluesky 🦋 profile</title>
      <dc:creator>jnsahaj</dc:creator>
      <pubDate>Sat, 07 Dec 2024 07:46:32 +0000</pubDate>
      <link>https://dev.to/sahajjj/free-insights-for-any-bluesky-profile-3nc8</link>
      <guid>https://dev.to/sahajjj/free-insights-for-any-bluesky-profile-3nc8</guid>
      <description>&lt;p&gt;Due to the open nature of Bluesky's ATP (at-protocol), it is possible to create an interesting analytics tool for any user for free.&lt;/p&gt;

&lt;p&gt;So, I built one.&lt;br&gt;
Check it out at: &lt;a href="https://bskyinsights.com" rel="noopener noreferrer"&gt;bskyinsights.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftugy2ewm8oumxlveal5n.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftugy2ewm8oumxlveal5n.jpg" alt="Image description" width="800" height="649"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fp318uym85323kdn0qt73.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fp318uym85323kdn0qt73.jpg" alt="Image description" width="800" height="940"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>bluesky</category>
      <category>atprotocol</category>
      <category>webdev</category>
      <category>analytics</category>
    </item>
    <item>
      <title>Writing Commit Messages using AI from CLI (no API key)</title>
      <dc:creator>jnsahaj</dc:creator>
      <pubDate>Thu, 07 Nov 2024 11:11:10 +0000</pubDate>
      <link>https://dev.to/sahajjj/writing-commit-messages-using-ai-no-api-key-19nk</link>
      <guid>https://dev.to/sahajjj/writing-commit-messages-using-ai-no-api-key-19nk</guid>
      <description>&lt;h2&gt;
  
  
  Disclaimer
&lt;/h2&gt;

&lt;p&gt;Commit messages are important pieces of information, and serve as logical checkpoints for your work. I believe in writing informative commit messages that capture both the nuance and scope of the changes. The tool is an experiment to evaluate if AI-generated commit messages can fit in the workflow, if they can make it easier to write better commits.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tool
&lt;/h2&gt;

&lt;p&gt;I built an open-source CLI tool in Rust.&lt;br&gt;
Check it out: &lt;a href="https://github.com/jnsahaj/lumen" rel="noopener noreferrer"&gt;https://github.com/jnsahaj/lumen&lt;/a&gt;. &lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimg.shields.io%2Fgithub%2Fstars%2Fjnsahaj%2Flumen" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimg.shields.io%2Fgithub%2Fstars%2Fjnsahaj%2Flumen" alt="GitHub Repo stars" width="82" height="20"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Features
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Generate commit message for staged changes&lt;/li&gt;
&lt;li&gt;Generate summary for changes in a git commit by providing its SHA-1&lt;/li&gt;
&lt;li&gt;Generate summary for changes in git diff (staged/unstaged)&lt;/li&gt;
&lt;li&gt;Fuzzy-search for the commit to generate a summary&lt;/li&gt;
&lt;li&gt;Free and unlimited - no API key required to work out of the box&lt;/li&gt;
&lt;li&gt;Pretty output formatting enabled by Markdown&lt;/li&gt;
&lt;li&gt;Supports multiple AI providers&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Here's a demo that fuzzy-finds a git commit, and then generates a summary for it &lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwl7zpqlebzcknm3z4tft.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwl7zpqlebzcknm3z4tft.gif" alt="Demo for lumen, generating commit summary" width="1200" height="750"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  AI is bad at nuance
&lt;/h2&gt;

&lt;p&gt;The LLM is good at capturing the "what" of the change, but it may not understand the "why" of the change. To help the AI, I added a &lt;code&gt;--context&lt;/code&gt; flag&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;lumen draft
&lt;span class="c"&gt;# Output: "chore(logs): Rotate log files daily"&lt;/span&gt;

lumen draft &lt;span class="nt"&gt;--context&lt;/span&gt; &lt;span class="s2"&gt;"reduce disk usage"&lt;/span&gt;
&lt;span class="c"&gt;# Output: "chore(logging): Implement daily log file rotation to optimize storage"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This allows for writing "lazy" commits that only capture the "why" of the change, leaving the "what" of the change to the AI&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;While I am apprehensive about writing commits using AI, and this tool might not be the most refined version of it, but I do believe it is a step in the right direction&lt;/p&gt;

</description>
      <category>ai</category>
      <category>git</category>
      <category>productivity</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
