https://prateeksharma.me/tags/claude-code/ Recent content in Claude Code on Prateek Sharma Hugo en-us Wed, 16 Sep 2026 00:00:00 +0000 https://prateeksharma.me/projects/git-why/ Wed, 16 Sep 2026 00:00:00 +0000 https://prateeksharma.me/projects/git-why/ <p>Chat history is where most of the reasoning behind a commit actually lives: why an approach was chosen, what alternative got rejected, what constraint ruled out the simpler option. None of that survives once the conversation is gone, even though <code>git log</code> still has the commit. <a href="https://github.com/pratts/git-why" target="_blank" rel="noopener noreferrer">git-why</a> is a Claude Code skill that closes that gap by writing the reasoning directly onto the commit itself, as a <code>git notes</code> entry.</p> https://prateeksharma.me/open-source/wazirx-postman-docs-sync-skill/ Wed, 02 Sep 2026 00:00:00 +0000 https://prateeksharma.me/open-source/wazirx-postman-docs-sync-skill/ <p><a href="https://prateeksharma.me/open-source/wazirx-postman-spec-alignment/">PR #7</a> fixed one concrete case of the Postman collection drifting from the live API: a wrong endpoint path and misplaced parameters on the Crypto Withdraw request. Since this collection is treated as ground truth by third-party tooling built against it, that kind of drift has a blast radius beyond the repo itself, so I turned the process I used to find and fix it into a <a href="https://github.com/WazirX/wazirx-api-postman/pull/8" target="_blank" rel="noopener noreferrer">Claude Code Skill</a> : a plain Markdown file (<code>.claude/skills/wazirx-postman-docs-sync/SKILL.md</code>) with instructions for an agent to fetch the real spec, compare method, path, parameter location, and types against each existing request, fix confirmed drift, and flag anything ambiguous rather than guess.</p>