<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Git on Prateek Sharma</title>
		<link>https://prateeksharma.me/tags/git/</link>
		<description>Recent content in Git on Prateek Sharma</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://prateeksharma.me/tags/git/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>git-why</title>
				<link>https://prateeksharma.me/projects/git-why/</link>
				<pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/projects/git-why/</guid>
				<description>&lt;p&gt;Chat history is where most of the reasoning behind a commit actually lives:&#xA;why an approach was chosen, what alternative got rejected, what constraint&#xA;ruled out the simpler option. None of that survives once the conversation is&#xA;gone, even though &lt;code&gt;git log&lt;/code&gt; still has the commit. &lt;a href=&#34;https://github.com/pratts/git-why&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;git-why&lt;/a&gt;&#xA;&#xA;is a Claude Code skill that closes that gap by writing the reasoning&#xA;directly onto the commit itself, as a &lt;code&gt;git notes&lt;/code&gt; entry.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
