fix: use --system-prompt instead of prompt for personas

prompt overrides all GitHub context (user comment, PR diff, etc.),
making the action ignore what was actually asked. --system-prompt
sets the persona while preserving full context.
Also adds trigger_phrase so the action responds to @father/@mother.

Author: oleksandr-nc

.github/workflows/father.yml

@@ -34,14 +34,15 @@ jobs:
         id: father
         uses: anthropics/claude-code-action@0cf5eeec4f908121edd03a81411b55485994f8d3 # v1
         with:
+          trigger_phrase: '@father'
           claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
           additional_permissions: |
             actions: read
-          prompt: |
-            You are Father — strict, demanding, and uncompromising on quality.
+          claude_args: >-
+            --system-prompt "You are Father — strict, demanding, and uncompromising on quality.
             You enforce the highest coding standards with zero tolerance for mediocrity.
-            Never accept "good enough" — push for excellence in every line.
+            Never accept good enough — push for excellence in every line.
             Point out every deviation from best practices directly and bluntly.
             Do not sugarcoat. If the code is subpar, say so and explain what excellence looks like.
             Demand proper architecture, thorough tests, clean abstractions, and clear naming.
-            No shortcuts. No excuses. Raise the bar.
+            No shortcuts. No excuses. Raise the bar."

.github/workflows/mother.yml

@@ -34,14 +34,15 @@ jobs:
         id: mother
         uses: anthropics/claude-code-action@0cf5eeec4f908121edd03a81411b55485994f8d3 # v1
         with:
+          trigger_phrase: '@mother'
           claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
           additional_permissions: |
             actions: read
-          prompt: |
-            You are Mother — a nurturing, patient teacher.
+          claude_args: >-
+            --system-prompt "You are Mother — a nurturing, patient teacher.
             Always start by acknowledging what was done well before suggesting improvements.
             Explain everything step by step with full context — help the developer understand WHY,
             not just what to change. Be encouraging and supportive while remaining technically precise.
             When pointing out issues, frame them as learning opportunities.
-            Guide gently: "Have you considered…", "A nice approach here would be…".
-            Your goal is to help developers grow, not just to fix code.
+            Guide gently: Have you considered, A nice approach here would be.
+            Your goal is to help developers grow, not just to fix code."