live-code-watch
Skill0 starsChanged 2 months agoApache-2.0View on GitHub
Watch a git repo's working diff get written live — a terminal that redraws ONLY when the code changes (no idle flicker), with brand-new files shown inline via intent-to-add. Point it at a repo while an AI agent (or you) edits and watch the raw code appear line by line. Zero deps beyond git. Use when the user says "watch the code", "show me the live diff", "watch this repo change", or wants to see edits happen in real time.
In this repository17 other files it gives its agents.
- aria-skill-candidatesSkill
- aria-skill-templateSkill
- aria-skill-testSkill
- call-scrubSkill
- cloudflare-dns-deploySkill
- doc-to-pdfSkill
- ffmpeg-audioSkill
- github-repo-deploySkill
- goal-to-planSkill
- headless-claudeSkill
- premortemSkill
- screen-describeSkill
- session-cabinetSkill
- skill-manifest-genSkill
- sprint-scaffoldSkill
- surgical-patchSkill
- video-ingestSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
When an AI agent edits your code (or you're pair-watching a build), git diff in a loop with clear *flickers* and you can't tell when …
- Distinctive: line 28
Read-only: the only mutation is a transient git add -N (intent-to-add).
- Distinctive: line 29
Not a git repo → prints a note and exits 0.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
live-code-watch
A live view of your repo's working diff that redraws only when the code changes.
python3 live_code_watch.py # render the current diff once, exit
python3 live_code_watch.py --watch # live: redraw only when it changes
python3 live_code_watch.py --repo ~/proj --watch --interval 1Why
When an AI agent edits your code (or you're pair-watching a build), git diff in a
loop with clear flickers and you can't tell when something actually changed.
This redraws only on change (cursor-home + clear-to-end), so it sits still when
idle and updates smoothly when code lands — and git add -N surfaces brand-new
files' contents in the diff.
Behavior
- Default (no flag): render the diff once and exit 0 — quick "what's changed."
--watch: live loop; redraws on change only.Ctrl-Cto stop.--max-iterations Nto auto-stop.- Read-only: the only mutation is a transient
git add -N(intent-to-add); it never commits. - Not a git repo → prints a note and exits 0.
Requires
giton PATH. No Python packages.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

