<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git Workflow on Top AI Skills</title><link>https://topaiskills.com/tags/git-workflow/</link><description>Recent content in Git Workflow on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/git-workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>Resolve Git Merge Conflicts With AI: The 5-Step Workflow</title><link>https://topaiskills.com/tutorials/guides/resolving-merge-conflicts-procedural/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/resolving-merge-conflicts-procedural/</guid><description>&lt;p&gt;Resolve every hunk, never run &lt;code&gt;--abort&lt;/code&gt;, and preserve both sides&amp;rsquo; intent — that&amp;rsquo;s the complete doctrine of Matt Pocock&amp;rsquo;s resolving-merge-conflicts skill (347.8K installs, #131 on the skills.sh all-time leaderboard). I read the SKILL.md out of the &lt;a href="https://github.com/mattpocock/skills" rel="nofollow" target="_blank"&gt;mattpocock/skills&lt;/a&gt; repo (233K stars) after watching a coding agent hit its first real conflict: it stared at &lt;code&gt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;/code&gt; markers, picked the HEAD side, and silently deleted a feature branch&amp;rsquo;s work. The skill&amp;rsquo;s rules exist to stop exactly that. This guide walks the five steps in order, with the exact behaviors the skill demands at each one.&lt;/p&gt;</description></item></channel></rss>