<?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: Karanveer</title>
    <description>The latest articles on DEV Community by Karanveer (@iamkaran).</description>
    <link>https://dev.to/iamkaran</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2762941%2F50804075-23c4-4ff5-8297-fd62acf1c0df.jpg</url>
      <title>DEV Community: Karanveer</title>
      <link>https://dev.to/iamkaran</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/iamkaran"/>
    <language>en</language>
    <item>
      <title>add whats, explains command (no llm)</title>
      <dc:creator>Karanveer</dc:creator>
      <pubDate>Tue, 28 Jul 2026 13:01:50 +0000</pubDate>
      <link>https://dev.to/iamkaran/add-whats-explains-command-no-llm-2ip6</link>
      <guid>https://dev.to/iamkaran/add-whats-explains-command-no-llm-2ip6</guid>
      <description>&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F83gm211r2sipfwjisdii.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F83gm211r2sipfwjisdii.gif" alt="demo" width="700" height="300"&gt;&lt;/a&gt;&lt;br&gt;
add 'whats' infront of any command and it explains it: flags, sub commands etc in a structutred format whereas something like manpage would throw the entire manual at you&lt;/p&gt;

&lt;p&gt;just pure man pages and help output&lt;/p&gt;

&lt;h1&gt;
  
  
  Q Why use &lt;code&gt;whats&lt;/code&gt; when we have man pages and --help
&lt;/h1&gt;

&lt;blockquote&gt;
&lt;p&gt;Yes you can use them but they throw the entire manual at you whereas you might have just needed one flag, whats outputs a structured format with the definitions you need&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h1&gt;
  
  
  Q Is it entirely offline? Does it use LLM
&lt;/h1&gt;

&lt;blockquote&gt;
&lt;p&gt;Yes absolutely, it just relies on man pages and if not then --help output of the binary itself,&lt;/p&gt;

&lt;p&gt;no it does not use llm at all&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h1&gt;
  
  
  Q If it uses regex then why cant i just use grep/sed instead of this?
&lt;/h1&gt;

&lt;blockquote&gt;
&lt;p&gt;a grep/sed command cannot find the descriptions of sub commands along with flags, it cant find descriptions of sub commands of sub commands, it probable cant use other sources as a fallback too&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h1&gt;
  
  
  Q What about tldr?
&lt;/h1&gt;

&lt;blockquote&gt;
&lt;p&gt;Even with tldr, you have to look for the flags you need instead of it providing the ones you need automatically in one go&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;if you like the idea then maybe star?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/iamkaran/whats" rel="noopener noreferrer"&gt;https://github.com/iamkaran/whats&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
