Solo developer

Find out before the build does

“The build fails on something I could have caught on my own machine.”

A workflow searches your code on a schedule, speaks up only when it finds something that blocks, and leaves what it found on a board. No AI runs in it, so checking costs nothing.

1. 1

   Set the search running on its own

   Start blank in the Workflows panel, give it a schedule, and add a search step. It calls the built-in file search rather than a model, so a run costs nothing and works offline.

   Try this

   Copy

   Every hour, search <your project folder> for lines containing FIXME and lines containing TODO, and count each one separately.

   Dynamic Workflows→

   4:52

   What happens in this clip

   1. Start from an empty canvas.
   2. Put the workflow on a clock.
   3. Add steps from the rail by name, then fill in the fields each tool asks for.
   4. Branch on what the previous step found.
   5. Save it and run it. Then the same workflow again from one sentence, drafted for you to read before it can run.

2. 2

   Say what counts as a problem

   A condition splits the run in two. The markers that block a release raise a notification that opens the folder when you click it. Everything else finishes quietly.

   Dynamic Workflows→

   1:46

   What happens in this clip

   1. A bundled workflow opens in the editor.
   2. The trigger at the top polls the inbox.
   3. A tool step reads the email, spending no AI tokens.
   4. An AI step pulls out named fields, and a branch decides what happens next.
   5. A message step sends the reply, and a notification step tells you it went.

3. 3

   Shape the result on the way out

   The last step turns the counts into tiles and a table, using small recipes rather than hand-written code. Whatever runs last is what a board reads, so it pays to shape it on purpose.

   Dynamic Workflows→

   

4. 4

   Put the last run on a board

   Add a stat tile and point it at the workflow instead of a tool. It reads the newest finished run rather than starting one, so the tiles are free to keep on screen. A table beside them names the file and line behind every marker.

   Try this

   Copy

   Build me a board from that workflow: a tile per count, red when the blocking one is above zero, and a table of every marker with its file and line.

   Dashboards→

   

5. 5

   Leave it watching while you work

   Turn on monitoring and the board stays current with the panel closed. Three failed runs in a row switch the workflow off and tell you, so a check that quietly broke cannot keep looking green.

   Dashboards→

   

6. 6

   Turn what is left into a list you can work through

   The markers that do not block are still work. Each one can be filed as a task pointing at the folder it came from, so they land on the board with the rest of your work rather than sitting in the code.

   Try this

   Copy

   For every TODO that run found, add a task in Projects pointing at that file, and skip the ones I already have.

   Projects→