- require commit descriptions to include a concise title and a detailed body when warranted by the change scope
- require the proposed git commit command to match the full approved message, including the detailed body
- document that execution should not collapse an approved full commit message to only the short title
Update the git guide so the assistant does not execute git push commands when credentials or SSH key passphrases might be required. Instead, the assistant must show the exact push command and direct the user to run it directly in the terminal.
Keep the existing rule that passwords and passphrases must not be accepted through chat and that password handoff requests must be refused.
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.
Document the repo preference that commit-description requests must show the proposed commit message first, followed by the exact git commit command and the exact git push -u origin main command that would be executed.
Require explicit user approval before running either command, and document that push operations should default to git push -u origin main with an interactive handoff at any password or SSH key passphrase prompt.
Update git-guide.md to document the repository URL used for this workspace as the current origin.
Require showing the exact git commit command alongside proposed commit messages.
Wait for explicit approval before creating a commit.
Document the repo-specific git workflow for /home/aw/code/cds. Require drafting commit messages for user review before running git commit, and keep commits scoped to the approved change.
