<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/f9a7db55217e4f21aa294de038cd08dc&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f9a7db55217e4f21aa294de038cd08dc-085ea7b2e3427c12.gif</thumbnail_url><duration>423.174</duration><title>Vibe-Coding a Git History Tool with Claude Code 🚀</title><description>I&apos;ve been working on a project using CloudCode over the weekend, inspired by LazyGit, to create a tool that allows users to navigate the history of specific files in their Git repositories. This tool, built in Rust, lets you see the commit history for a file and keeps track of the line you&apos;re on as you move through the history, which is a key feature. I brainstormed the specifications with Gemini and used Claude Code to help implement the functionality, including debugging strategies and code assessments. Currently, I&apos;m addressing some CI issues with GitHub, and I would appreciate any insights or suggestions on resolving these failures.</description></oembed>