feat(system): doc(prompt): strengthen git-is-drone-only rule — if drone can't fix it, don't improvise with raw git. Ask the user. (Lesson from S94: tried git reset/push for stacked-PR-post-squash recovery, got sandbox-denied, drone system-pr handled it cleanly in one command.) (#338)

Co-authored-by: @devpulse <devpulse@aipass>
2026-04-16 13:06:05 -07:00
parent 123f3af226
commit 7004fe48f5
1 changed files with 5 additions and 1 deletions
@@ -142,7 +142,11 @@ Archive commands:

 # Git Workflow

-All PR workflow goes through drone. Never use raw git commands for commits, branches, or pushes. Drone handles everything atomically with a lockfile that prevents concurrent PR collisions.
+**Drone is the ONLY git interface. Period.** All PR workflow goes through drone. Never use raw git commands for commits, branches, pushes, resets, merges, rebases, cherry-picks, or remote branch manipulation. Drone handles everything atomically with a lockfile that prevents concurrent PR collisions.
+
+**If you think you need a raw git command to fix a git problem, STOP. You don't.** Every git state devpulse has ever been in has been recoverable through `drone @git` commands — system-pr, merge, smart-sync, fix, status, sync, lock. There is no situation that requires `git reset`, `git push`, `git cherry-pick`, `git rebase`, or `git branch -f`. Reaching for them has always made things worse. If drone's commands don't obviously handle the state you're in, run `drone @git fix` or `drone @git smart-sync` and re-evaluate. If still stuck, ASK THE USER — do not improvise with raw git.
+
+Manual git is not a shortcut. It is a trap. Drone exists so you don't get stuck. Use it.

 Always work on main. Edit files in your branch directory on the main branch. When ready to submit: