Fix broken git demos/labs in Modules 4, 7, 14 (#2,#3,#4,#12) (#55)
Co-authored-by: claude <claude@jpaul.io> Co-committed-by: claude <claude@jpaul.io>
This commit was merged in pull request #55.
This commit is contained in:
@@ -331,10 +331,24 @@ copy-paste loop back in Module 1, now done right.
|
||||
It should add tasks, delete one by index, and confirm the right task remains. If it fails, don't
|
||||
hand-fix it — tell the AI what broke and let it iterate (step 4 of the loop), then re-run.
|
||||
|
||||
8. **Commit the reviewed change — this is your new checkpoint.** It passed your own eyes and it
|
||||
passes the check, so lock it in:
|
||||
|
||||
```bash
|
||||
git add .
|
||||
git commit -m "Add delete command (made via editor/CLI agent)"
|
||||
git log --oneline
|
||||
```
|
||||
|
||||
You just shipped a reviewed, multi-file change made by an AI editing your files directly — and the
|
||||
copy-paste loop never entered into it. This commit is now the clean state `git restore .` falls
|
||||
back to in the next part.
|
||||
|
||||
### Part D — Practice the revert (do this even though it works)
|
||||
|
||||
8. You only trust an undo you've used. Prove the net is under you: ask the tool for a deliberately
|
||||
throwaway change —
|
||||
9. You only trust an undo you've used. Your tree is clean — you just committed in Part C, which is
|
||||
exactly the safe setup the one rule demands. Prove the net is under you: ask the tool for a
|
||||
deliberately throwaway change —
|
||||
|
||||
> *"Rename every variable in `tasks.py` to single letters."*
|
||||
|
||||
@@ -348,18 +362,18 @@ copy-paste loop back in Module 1, now done right.
|
||||
|
||||
That's the Module 2 safety net catching a Module 4 mistake. Internalize how cheap that was.
|
||||
|
||||
### Part E — Commit the good change
|
||||
### Part E — Confirm you're back at your good state
|
||||
|
||||
9. Now commit the `delete` feature you kept in Part C (Part D's mess is already gone):
|
||||
10. Nothing left to commit — the `delete` feature went in back in Part C, and Part D's throwaway is
|
||||
already gone. Confirm the reviewed multi-file commit is your latest and the tree is clean:
|
||||
|
||||
```bash
|
||||
git add .
|
||||
git commit -m "Add delete command (made via editor/CLI agent)"
|
||||
git log --oneline
|
||||
```
|
||||
```bash
|
||||
git log --oneline # "Add delete command…" is the latest commit
|
||||
git status # clean — the throwaway left no trace
|
||||
```
|
||||
|
||||
You just shipped a reviewed, multi-file change made by an AI editing your files directly — and the
|
||||
copy-paste loop never entered into it.
|
||||
That's the whole loop closed: a reviewed, multi-file change the AI made across both files is
|
||||
committed, and the mess you made on purpose vanished without touching it.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user