conon.ai

conon.ai/Tips

Version Control In One Sentence

Say 'take this project under version control and commit the current state as v1' — no terminal, no commands to learn. From that point every change is diffable and every broken Friday rolls back to a working Thursday. Without the baseline there is no diff counter, no rollback, no safety net.

AdvancedTOOLSClaude Code

Why it works

One sentence — take this project under version control and commit the current state — buys a time machine for the whole folder: every change diffable, every broken Friday recoverable to a working Thursday. Without the baseline there is no diff counter, no rollback, no safety net; with it, the agent can break things bravely because breaking is reversible.

How to do it

  1. In the first session of any project, say: 'take this project under version control and commit the current state as version 1.'
  2. The agent runs the setup itself — you type no git commands, ever.
  3. Notice the change counter appear (+/− numbers): every future edit is now measured against a baseline.
  4. Before every big rework, checkpoint again: 'commit the current state as [name].'
  5. Connect the GitHub connector once to keep the history off-machine too.
  6. Disaster recovery is one sentence: 'roll back to the last committed version.'

Copy this

prompt
Take this project under version control and commit the current state as version 1.

What to watch for

  • Version control is not /rewind: rewind undoes the agent's recent edits; commits preserve everything — including YOUR manual changes — for as long as you keep them.
  • Commit BEFORE the risky experiment, not after noticing it went wrong; the checkpoint you need is the one from ten minutes ago.

Sources

Original: conon.aiDocumentation: code.claude.com

Read next

Scheduled Agents Need An Open Lid
Local scheduled tasks run only while the app is open and the machine is awake — a missed slot is skipped, not postponed. Turn on keep-awake, leave the laptop lid open, and write drift-tolerant instructions: 'if it's already past 5pm, skip today and report that you skipped'. Need lid-closed reliability? That's a cloud task — which can't see your local files.
Claude Code
Typed It Three Times? Make A Skill
The third time you type the same procedure is the signal: say 'create a skill that does this' and the agent writes the skill file itself. Then improve it in a loop — run it, note what's off, have it edit its own skill. House rules: 2nd repeated mistake → CLAUDE.md line; 3rd repeated prompt → skill.
Claude Code
Writer Session, Reviewer Session
Run two parallel sessions on one version-controlled project: one builds, the other — with fresh context — reviews. The docs are explicit about why it works: a fresh session isn't attached to code it didn't write, so it critiques honestly where the author session defends.
Claude Code
Send Noisy Research To A Subagent
Any side-investigation that would flood your session — 'which of these fifty files mentions the old pricing?' — goes to a subagent. It reads everything inside its own separate memory and returns three lines; your session's context stays clean for the actual work.
Claude Code

We build and operate the systems behind tips like this one — agents, automations and internal tools, shipped into production. See what the studio does →