<?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: Mohamed Sawissi</title>
    <description>The latest articles on DEV Community by Mohamed Sawissi (@ayanmohamedali7blip).</description>
    <link>https://dev.to/ayanmohamedali7blip</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%2F4248541%2F1c730ac1-10ea-4dd7-af36-22f3475c8196.png</url>
      <title>DEV Community: Mohamed Sawissi</title>
      <link>https://dev.to/ayanmohamedali7blip</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ayanmohamedali7blip"/>
    <language>en</language>
    <item>
      <title>Building Patchwork with Kiro: making a codebase remember why</title>
      <dc:creator>Mohamed Sawissi</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:54:42 +0000</pubDate>
      <link>https://dev.to/ayanmohamedali7blip/building-patchwork-with-kiro-making-a-codebase-remember-why-4f5f</link>
      <guid>https://dev.to/ayanmohamedali7blip/building-patchwork-with-kiro-making-a-codebase-remember-why-4f5f</guid>
      <description>&lt;p&gt;&lt;em&gt;Written as part of the Kiroween 2026 hackathon.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Every file in a large codebase was shaped by many engineers over years. Each change was made for a reason — a money-safety fix, a security lock, a pricing correction. But that reasoning lives in commit history almost nobody reads. When an engineer leaves, the &lt;em&gt;why&lt;/em&gt; leaves with them, and the next person quietly reintroduces a bug that was fixed on purpose two years ago.&lt;/p&gt;

&lt;p&gt;For Kiroween 2026 I built &lt;strong&gt;Patchwork&lt;/strong&gt; to fix that. You point it at a GitHub pull request; for each changed file it reconstructs the knowledge behind that area of the code from its history, and warns you — before you merge — if your change undoes a decision someone made on purpose. And it cites the exact commit the warning comes from, so it never just makes things up.&lt;/p&gt;

&lt;p&gt;It works on real repositories. Run it on &lt;code&gt;expressjs/express&lt;/code&gt; and it catches that lowering the &lt;code&gt;body-parser&lt;/code&gt; version would reintroduce a documented CVE fix, and it names the commit that fixed it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Live app: &lt;a href="https://patchwork-1-axbd.onrender.com" rel="noopener noreferrer"&gt;https://patchwork-1-axbd.onrender.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Code: &lt;a href="https://github.com/ayanmohamedali7-blip/patchwork" rel="noopener noreferrer"&gt;https://github.com/ayanmohamedali7-blip/patchwork&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Demo video: &lt;a href="https://youtu.be/n4cjcSygvcU" rel="noopener noreferrer"&gt;https://youtu.be/n4cjcSygvcU&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Frankenstein angle
&lt;/h2&gt;

&lt;p&gt;Patchwork fits Kiroween's &lt;em&gt;Frankenstein&lt;/em&gt; category: it stitches together the expertise of every engineer who shaped an area of the code into one assistant that guards it — a creation assembled from many contributors' knowledge, built in an inventor's workshop. Nothing supernatural; just history, made to speak at the moment it matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I built it with Kiro
&lt;/h2&gt;

&lt;p&gt;This is the part I actually want to talk about, because building &lt;em&gt;with&lt;/em&gt; Kiro was different from how I usually work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Spec-first, not vibe-first.&lt;/strong&gt; Instead of jumping into code, I wrote the feature as a spec: requirements (EARS-style acceptance criteria), a design doc, and a task list, all under &lt;code&gt;/.kiro/specs&lt;/code&gt;. That sounds like overhead, but it kept the whole build honest — every module traced back to a requirement, and I made one deliberate design decision early (one shared "knowledge builder" feeding both the local-git and GitHub-API paths) that saved me from duplicating logic later.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Steering docs did the "remembering" for me.&lt;/strong&gt; I put the stack, the folder structure, and a hard rule about the project's theme into &lt;code&gt;/.kiro/steering&lt;/code&gt;. After that, when I asked Kiro's agent to add something, it read the steering first and matched my conventions without me repeating them every time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The moment it clicked.&lt;/strong&gt; I asked Kiro's agent to add a small feature — a one-line, history-grounded "next step" on every warning. It explored the project, ran my test suite to establish a baseline (4/4 passing), implemented the change across the review engine and the UI, and kept the tests green — all from a single prompt, following the steering docs. That was the first time an AI tool felt like it was building &lt;em&gt;with&lt;/em&gt; me, not autocompleting under me.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hooks and MCP.&lt;/strong&gt; I wired two agent hooks: a "dogfood" hook that runs Patchwork's own review on each source save (the tool guards the tool), and a syntax-guard hook that runs &lt;code&gt;node --check&lt;/code&gt; across the source after each turn so a broken edit never lingers. I also configured a GitHub MCP server so the agent could read repositories while building — fitting, for a tool that is all about reading git history.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell someone starting with Kiro
&lt;/h2&gt;

&lt;p&gt;Write the spec and the steering docs first, even if it feels slow. That's what turns the agent from a fast autocomplete into something that builds the thing you actually meant. The specs, steering, hooks and MCP config are all committed in the repo's &lt;code&gt;/.kiro&lt;/code&gt; directory if you want to see exactly how it's set up.&lt;/p&gt;

&lt;p&gt;Patchwork — the knowledge behind your code, stitched back together, so a change never breaks what someone built on purpose. Built with Kiro.&lt;/p&gt;

</description>
      <category>kiro</category>
      <category>hackathon</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
