FIELD NOTES / AI × BASH

I prompt.
We build.
Git push.

A model with a terminal can do a lot. A good harness turns those commands into work you can inspect, repeat, and trust.

●●●bash — inside the harness

# 01 / understand the workspace
$ pwd && git status --short
$ rg -n 'TODO|FIXME' src/

# 02 / make one focused change
$ git diff --check
$ npm test
✓ checks passed

# 03 / review before shipping
$ git diff --stat
$ git diff
▍

01 / inspect02 / change03 / verify04 / review & ship

SMALL COMMANDS. VISIBLE PROGRESS.

The shell is the feedback loop.

[01]

Read the real thing.

Start with files, logs, and the current Git diff. Give the model evidence from the workspace so its next step has a concrete basis.

[02]

Keep the scope small.

Run focused commands in a known directory. Capture stdout, stderr, and exit codes. Make each change easy to explain and undo.

[03]

Close the loop.

Run the relevant checks, read their results, and inspect the patch. Commit and push when the work is ready and publishing is authorized.

NOTE 001 / THE BORING PARTS MATTER

A little Bash.
A lot of context.

The harness carries the working directory, permissions, and tool output between steps. Bash connects the tools you already use. Together, they make a useful place to build.

Prefer clear commands, bounded output, and a reviewable diff. Keep secrets out of logs. Let the result of each command guide the next.

# A quick review checkpoint
set -euo pipefail

git status --short
git diff --check
git diff --stat

# Then inspect the actual patch.
git diff