From 9b4eee0c1fa00b59eebd7068dea0d8e79425c89b Mon Sep 17 00:00:00 2001 From: John O'Keefe Date: Tue, 24 Feb 2026 10:46:30 -0500 Subject: [PATCH] docs: add git workflow guidelines for sequential command execution --- PROJECT_GUIDELINES.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/PROJECT_GUIDELINES.md b/PROJECT_GUIDELINES.md index b83a70a..478c36f 100644 --- a/PROJECT_GUIDELINES.md +++ b/PROJECT_GUIDELINES.md @@ -47,8 +47,14 @@ - ❌ **NEVER delete code without reading full context first** (minimum 20 lines before/after) - ❌ **NEVER make cascading fix-up edits without git diff review** - After compilation error: STOP, review `git diff`, understand full impact - - Use revert/re-apply pattern instead of blind fixes + - Use revert/reapply pattern instead of blind fixes - ❌ **NEVER skip post-edit verification** - must compile after each file edit +- ❌ **NEVER run git commands concurrently** - always run sequentially: + - Run `git add ` and wait for completion + - Run `git commit -m ""` and wait for completion + - Run `git push` and wait for completion + - Never use `&&` to chain git commands together +- ✅ **Make good organized git commits for the entire project (not just what you changed) and push - run git add, commit, push sequentially as separate commands, no need to repeatedly check status** ### Cascading Fix-up Pattern (PROHIBITED)