Skip to content

Instantly share code, notes, and snippets.

@ljw1004

ljw1004/you_are_not_right.sh

Last active November 2, 2025 20:11
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save ljw1004/34b58090c16ee6d5e6f13fce07463a31 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save ljw1004/34b58090c16ee6d5e6f13fce07463a31 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. ljw1004 revised this gist Aug 5, 2025. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion you_are_not_right.sh
    View file
    Original file line number Diff line number Diff line change
    @@ -30,7 +30,8 @@ while IFS= read -r item; do
    text=$(jq -r '.message.content[0].text' <<< "$item")
    [[ "${text:0:80}" =~ .*[Yy]ou.*(right|correct) ]] && needs_reminder=true
    [[ "${text:0:80}" =~ .*[Aa]bsolutely ]] && needs_reminder=true

    [[ "${text:0:80}" =~ .*사용자가.*맞다 ]] && needs_reminder=true # Korean
    [[ "${text:0:80}" =~ .*맞습니다 ]] && needs_reminder=true # Korean
    done <<< "$items"
    [[ "$needs_reminder" == "true" ]] || exit 0

  2. ljw1004 created this gist Aug 4, 2025.
    69 changes: 69 additions & 0 deletions you_are_not_right.sh
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,69 @@
    #!/bin/bash
    set -euo pipefail
    trap 'echo "at line $LINENO, exit code $? from $BASH_COMMAND" >&2; exit 1' ERR

    # This is a Claude Code hook to stop it saying "you are right".
    #
    # Installation:
    # 1. Save this script and chmod +x it to make it executable.
    # 2. Within Claude Code, /hooks / UserPromptSubmit > Add a new hook (this file)
    #
    # How it works:
    # This script checks whether the assistant has recently told the user they are right.
    # If so, it appends a system-reminder to the following user prompt,
    # reminding the assistant not to do that, and giving it constructive
    # examples of how it should respond to the user instead.

    stdin=$(cat)
    transcript_path=$(echo "$stdin" | jq -r ".transcript_path")

    # We'll look through the last 5 items in the transcript.
    # Sometimes the final item will be assistant thinking,
    # and the previous one will be "you're right".
    # We'll look for any triggering phrase like "You're right"
    # or "you are absolutely correct".
    items=$(grep '"role":"assistant"' "$transcript_path" | tail -n 5)
    needs_reminder=false
    while IFS= read -r item; do
    [[ "$(jq -r '.type // empty' <<< "$item")" == "assistant" ]] || continue
    [[ "$(jq -r '.message.content[0].type // empty' <<< "$item")" == "text" ]] || continue
    text=$(jq -r '.message.content[0].text' <<< "$item")
    [[ "${text:0:80}" =~ .*[Yy]ou.*(right|correct) ]] && needs_reminder=true
    [[ "${text:0:80}" =~ .*[Aa]bsolutely ]] && needs_reminder=true

    done <<< "$items"
    [[ "$needs_reminder" == "true" ]] || exit 0

    # upon exit code 0, Claude Code will append stdout to the context
    # and proceed.
    cat <<'EOF'
    <system-reminder>
    You MUST NEVER use the phrase 'you are right' or similar.
    Avoid reflexive agreement. Instead, provide substantive technical analysis.
    You must always look for flaws, bugs, loopholes, counter-examples,
    invalid assumptions in what the user writes. If you find none,
    and find that the user is correct, you must state that dispassionately
    and with a concrete specific reason for why you agree, before
    continuing with your work.
    <example>
    user: It's failing on empty inputs, so we should add a null-check.
    assistant: That approach seems to avoid the immediate issue.
    However it's not idiomatic, and hasn't considered the edge case
    of an empty string. A more general approach would be to check
    for falsy values.
    </example>
    <example>
    user: I'm concerned that we haven't handled connection failure.
    assistant: [thinks hard] I do indeed spot a connection failure
    edge case: if the connection attempt on line 42 fails, then
    the catch handler on line 49 won't catch it.
    [ultrathinks] The most elegant and rigorous solution would be
    to move failure handling up to the caller.
    </example>
    </system-reminder>
    EOF

    exit 0