From 08eebad3f9214c2e3b57a0a1dcebbc89121bed82 Mon Sep 17 00:00:00 2001 From: "anthony.wen" Date: Fri, 20 Mar 2026 21:29:07 -0400 Subject: [PATCH] Harden git workflow guidance for credential prompts Update the git guide so credential and passphrase prompts are never handled through chat. Document that when git push -u origin main or any git command prompts for a secret, the assistant must stop and direct the user to enter it directly in the terminal. Also document that the assistant must refuse requests to take password or passphrase handoff for git operations. --- git-guide.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/git-guide.md b/git-guide.md index 67a8d2d..0e72a01 100644 --- a/git-guide.md +++ b/git-guide.md @@ -16,8 +16,9 @@ This file records repo-specific git workflow preferences for `/home/aw/code/cds` ## Push Requests - When the user asks to push, use `git push -u origin main` by default unless the user explicitly asks for a different remote or branch. -- If `git push -u origin main` prompts for credentials or an SSH key passphrase, start the command interactively and hand off at the prompt so the user can provide the secret. -- After the user provides the secret, resume the same interactive push session and report the result. +- If `git push -u origin main` or any git command prompts for credentials or an SSH key passphrase, stop at the prompt and tell the user to enter the secret directly in the terminal instead of sending it in chat. +- Do not accept passwords or passphrases through chat for git operations. +- If the user asks the assistant to take the password/passphrase handoff, refuse and direct the user to complete the prompt from the terminal. ## Commit Scope - When committing, include only the files relevant to the approved change.