<?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: nexus ai</title>
    <description>The latest articles on DEV Community by nexus ai (@workflownexus).</description>
    <link>https://dev.to/workflownexus</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%2F4254521%2F857f8eb7-607b-4142-b1fd-cda70eca6671.jpg</url>
      <title>DEV Community: nexus ai</title>
      <link>https://dev.to/workflownexus</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/workflownexus"/>
    <language>en</language>
    <item>
      <title>6 Repeatable Aider Workflows (and the Git Routine That Makes Them Safe)</title>
      <dc:creator>nexus ai</dc:creator>
      <pubDate>Thu, 19 Nov 2026 21:39:46 +0000</pubDate>
      <link>https://dev.to/workflownexus/6-repeatable-aider-workflows-and-the-git-routine-that-makes-them-safe-3ffl</link>
      <guid>https://dev.to/workflownexus/6-repeatable-aider-workflows-and-the-git-routine-that-makes-them-safe-3ffl</guid>
      <description>&lt;p&gt;After a few months of using Aider — the open-source AI pair-programming tool that lives in your terminal — as my daily driver, I noticed my sessions weren't random. They fell into the same six patterns. Writing them down as repeatable workflows changed my results more than any prompt trick.&lt;/p&gt;

&lt;h2&gt;
  
  
  The six workflows
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Greenfield Scaffold.&lt;/strong&gt; For a new tool or script: start from a spec, not a wish. Language and version, allowed dependencies, inputs, outputs, one concrete example. Scaffold the smallest runnable spine, run it yourself, and grow it later — never ask for the whole app in one prompt.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Feature Add on Existing Code.&lt;/strong&gt; Add the files that will change, mark the files the model should only &lt;em&gt;read&lt;/em&gt; (interfaces, schemas) as read-only, and ask for a plan before any code: which files change, what new behaviour appears, what could break. Read the plan critically. If the plan is wrong, re-plan — don't patch a bad plan with five micro-prompts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Test-Driven Bugfix Loop.&lt;/strong&gt; No failing test, no loop — without one, the model "fixes" by vibes. Write (or generate, then verify) a test that fails for the right reason, turn on &lt;code&gt;auto-test&lt;/code&gt; with your test command, and prompt with the symptom plus "fix the code, not the tests". A good fix is small and explainable in one sentence.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Planned Refactor (Architect Mode).&lt;/strong&gt; Precondition: a passing test suite. Ask the strong model for a file-by-file plan with one invariant — no behaviour changes — then let the editor model execute. A refactor never shares a commit with a feature.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Test Generation.&lt;/strong&gt; Prompt for &lt;em&gt;behaviour&lt;/em&gt; tests with named edge cases (empty input, Unicode, missing files), then do the step most people skip: mutate the code by hand — an off-by-one is enough — and confirm a test catches it. Tests that can't fail are decoration.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Onboarding to an Unfamiliar Codebase.&lt;/strong&gt; Start with no files added and stay in ask mode: What does this project do? Where is the entry point? Trace a request through a feature — which files, in what order? Save the answers as notes. Only then make your first real change, in a small, well-understood corner.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Git routine that makes this safe
&lt;/h2&gt;

&lt;p&gt;Aider's real superpower is that every generation is a git commit you can inspect and reverse. My routine:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One config change:&lt;/strong&gt; &lt;code&gt;dirty-commits: false&lt;/code&gt; in &lt;code&gt;.aider.conf.yml&lt;/code&gt;, so Aider never commits my uncommitted work for me — and I still commit or stash my own work before a session, deliberately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review every AI change like a PR:&lt;/strong&gt; read the diff hunk by hunk (especially deletions, tests, and anything touching config or data), then run the tests myself at least once per session, even with auto-test on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Know your undo ladder:&lt;/strong&gt; &lt;code&gt;/undo&lt;/code&gt; in chat for the last Aider commit, &lt;code&gt;git revert&lt;/code&gt; for a later bad commit on a shared branch, and task branches as your blast-radius limiter — never let Aider work directly on your deployment branch while you're learning.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Pick the model per workflow, not per project
&lt;/h2&gt;

&lt;p&gt;Architect mode for refactors, a cheaper model for test generation, your best model only where judgement matters. This cut my API spend more than any other single change.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Full disclosure: I packaged these workflows with the full Git safety guide (complete undo ladder, branching strategy, pre-push checklist), a cost-control guide with a model-selection matrix, and the templates I use (task brief, prompt starters, review/commit checklists, full &lt;code&gt;.aider.conf.yml&lt;/code&gt;) as a $10 pack: &lt;a href="https://whop.com/checkout/plan_Qnb9d21JZ7LEa" rel="noopener noreferrer"&gt;https://whop.com/checkout/plan_Qnb9d21JZ7LEa&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;New to Aider? Start with the free Starter Kit instead — it covers installation and your first session: &lt;a href="https://whop.com/checkout/plan_diZ6ymgxjRMz2" rel="noopener noreferrer"&gt;https://whop.com/checkout/plan_diZ6ymgxjRMz2&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>programming</category>
      <category>git</category>
    </item>
  </channel>
</rss>
