Prompt file imported from agreaves-ms/hve-ado-scaffold (.github/prompts/git-setup.prompt.md). Fill in {{userName}}, {{userEmail}}, {{repoPath}} before use. Copyright stays with the author.

Git Environment Setup (Verification-First)

You WILL help the user ensure their Git environment is consistently configured for everyday workflows (git add, commit, fetch, pull, push) without overwriting existing preferred settings. You MUST verify current values before suggesting changes. You MUST never unilaterally modify configuration; always propose and ask for confirmation.

Goals

• Ensure identity: user.name, user.email set.
• Ensure consistent editing & diff/merge tooling (code-based tools) when not already configured.
• Optionally assist with commit signing (GPG or SSH) ONLY if the user explicitly requests it or indicates a signing-related error.
• Optionally assist with adding safe.directory ONLY if the user reports a Git safety error mentioning ownership / unsafe repository.
• Keep existing customizations intact; do NOT downgrade or remove existing settings.

High-Level Protocol

1. Detect current context.
2. Report missing or desirable improvements.
3. Propose minimal, explicit remediation commands (group logically).
4. Ask for confirmation per group before applying.
5. Never apply changes not explicitly confirmed.
6. Summarize applied changes and remaining optional improvements.

Tools & Constraints

• Initial audit MUST run exactly one command to gather the full baseline: git config --list --show-origin (captures values plus their source). No additional lookup commands during baseline collection.
• If (and only if) later a single specific value needs clarification (e.g., ambiguity due to multiple matches), you MAY propose a single follow-up git config --get <key> after user confirmation; avoid batches.
• Do NOT execute any gpg or ssh-keygen commands during the initial audit phase.
• Only propose (do not run) a gpg --list-secret-keys command IF and ONLY IF signing is enabled (commit.gpgSign=true) OR the user explicitly requests to enable signing and lacks clarity on available keys.
• Only propose (do not run) key generation (GPG or SSH) if the user explicitly opts into signing and no existing key info is discoverable via config.
• Commands shown MUST be simple, one per line, directly runnable, and human-auditable.
• Do NOT show secrets (redact emails only if user requests privacy).
• Do NOT push, fetch, pull, or alter remotes; only configuration steps explicitly confirmed.

Detection Steps

Perform and present results in this order using ONLY the single baseline command output (git config --list --show-origin) for the initial audit (no GPG/SSH commands during this phase):

1. Identity: Parse user.name, user.email (note scope from origin path). If absent in any scope, mark MISSING.
2. Commit Signing (Passive Scan Only): Parse commit.gpgSign, gpg.format, user.signingkey. Classify status (for display only; do NOT propose changes unless user asks):
   • Disabled: commit.gpgSign false/unset.
   • Configured Candidate: signing true AND both gpg.format & user.signingkey present.
   • Incomplete: signing true but one of gpg.format / user.signingkey missing.
   • Not Configured: all unset. Deeper validation (key listing) only upon explicit user request.
3. Editor & Tools: Parse core.editor, diff.tool, merge.tool. Mark any missing as GAP.
4. Safe Directory: From any safe.directory entries in the baseline output, note whether current repo path is included. Only propose adding if the user later reports an unsafe repository warning.
5. Line Endings: Parse core.autocrlf, core.eol. Flag only if both unset and user later indicates cross-platform needs.

Proposal Logic

• For each GAP (identity, editor/tools) build a remediation group with: rationale, exact single-line commands, expected effect.
• Signing: ONLY build a remediation group if the user explicitly asks about signing, indicates they want to enable/disable it, or reports a signing verification error.
• Safe Directory: ONLY build a remediation group if the user reports an unsafe repository error message from Git.
• Line endings: Offer only if user mentions cross-platform concerns.
• Each command stands alone (no chaining with &&, ;, pipes, or subshells) to maximize transparency and trust.
• Signing validation / key listing commands appear only after explicit user request.
• Key generation commands appear only if user requests and no usable key reference exists.
• Use idempotent commands (setting an already-correct value is acceptable if user confirms).

Commands Templates (Examples)

Do NOT emit these unless needed; adapt values after user confirmation. Each command is intentionally minimal and isolated.

# initialize a new git repository (if needed)
git init
# Single baseline audit (read-only; captures all keys and their source files):
git config --list --show-origin

git config --global user.name "{{userName}}"      # Sets global author identity (verify before applying)
git config --global user.email "{{userEmail}}"    # Must be a valid email format

# If signing misconfigured and user opts to disable for now:
git config --global commit.gpgSign false

git config --global --add safe.directory "{{repoPath}}"  # Trust this repository path (run only after unsafe repo error)

# Enable SSH-based signing (requires Git >=2.34 and configured SSH key)
git config --global gpg.format ssh
git config --global user.signingkey "~/.ssh/id_ed25519.pub"
git config --global commit.gpgSign true

# (Only propose after user explicitly opts in and no key present)
gpg --full-generate-key
gpg --list-secret-keys --keyid-format=long
gpg --armor --export <KEY_ID> > public-gpg-key.asc
git config --global gpg.format openpgp
git config --global user.signingkey <KEY_ID>
git config --global commit.gpgSign true

# Generate a new Ed25519 SSH key for signing
# Linux/macOS (bash/zsh):
ssh-keygen -t ed25519 -C "{{userEmail}}" -f ~/.ssh/id_ed25519

# Windows PowerShell:
ssh-keygen -t ed25519 -C "{{userEmail}}" -f $HOME/.ssh/id_ed25519

# Start ssh-agent and add key (Linux/macOS):
eval "$(ssh-agent -s)" && ssh-add ~/.ssh/id_ed25519
# PowerShell (OpenSSH built-in):
Start-SSHAgent; ssh-add $HOME/.ssh/id_ed25519

# Configure Git to sign with SSH key
git config --global gpg.format ssh
git config --global user.signingkey ~/.ssh/id_ed25519.pub
git config --global commit.gpgSign true

# Configure VS Code as default editor, diff, and merge tools (only if currently unset):
git config --global core.editor "code --wait --new-window"

# Diff tool integration
git config --global diff.tool code
git config --global difftool.code.cmd 'code -n --wait --diff "$LOCAL" "$REMOTE"'

# Merge tool integration
git config --global merge.tool code
git config --global mergetool.code.cmd 'code -n --wait --merge "$REMOTE" "$LOCAL" "$BASE" "$MERGED"'
git config --global mergetool.code.trustexitcode true
git config --global mergetool.keepbackup false

Interaction Requirements

• Display a concise audit table (key | current | scope | status) BEFORE any proposals; audit uses only git config reads.
• After audit: ask only about identity/editor/tooling gaps automatically. Ask about signing or safe directory ONLY if the user mentioned them or an error context indicates relevance.
• For each remediation group: ask Apply identity fixes? (yes/no) style question.
• Accept explicit yes (case-insensitive). Any other response = no.
• After applying confirmed groups, re-read changed settings (again only with simple git config --get ...) to verify success and show a delta summary.

Edge Cases & Handling

• Missing identity: propose identity group.
• User explicitly asks for signing but misconfigured: propose signing fix or disable path.
• User reports unsafe repository error: propose safe.directory addition.
• user.email mismatch with corporate domain (if pattern provided by user later) -> warn only, do not change automatically.
• Already correct settings: state "No changes needed" and skip prompts except for explicitly asked topics.

Output Format

1. Audit section with headings and a REQUIRED summary table using emojis for clarity.
2. Emoji Table MUST include at least these columns: Setting | Value | Scope | Status. Use ✅ for satisfactory / present / consistent and ❌ for missing / inconsistent / needs attention. Optional columns (Notes) may be added for nuance.
3. Provide concise bullet notes below the table only for ❌ entries (do not restate ✅).
4. For each proposed group: explanation + fenced bash block + confirmation request line.
5. Post-application summary with successes and any remaining warnings; show a before → after mini-table if any changes applied.
6. Final status line: Git setup complete. or Git setup partial; user declined some changes.

Emoji Audit Table Example

| Setting         | Value                    | Scope   | Status | Notes |
|-----------------|--------------------------|---------|--------|-------|
| user.name       | Jane Doe                 | global  | ✅     |       |
| user.email      | (missing)                | -       | ❌     | required for commits |
| core.editor     | code --wait --new-window | global  | ✅     |       |
| diff.tool       | (unset)                  | -       | ❌     | optional convenience |
| merge.tool      | (unset)                  | -       | ❌     | improves merges |
| commit.gpgSign  | true                     | global  | ✅     | signing active |
| gpg.format      | ssh                      | global  | ✅     |         |
| user.signingkey | ~/.ssh/id_ed25519.pub    | global  | ✅     |         |
| safe.directory  | (not listed)             | -       | ✅     | not required (no unsafe warning) |

MUST NOT

• Must NOT unset or delete existing unrelated settings.
• Must NOT push/pull/fetch or modify remotes.
• Must NOT expose secrets or private key content.

Completion Criteria

• Either all critical gaps fixed (identity + chosen editor/tooling completeness) or explicitly declined by user with clear notice.
• Clear guidance for any remaining optional improvements (line endings, safe directory if applicable, signing if deferred).

Proceed by auditing the current Git configuration now by running the single baseline command above (no key or generation commands yet).