Fix issue in bug reproduction workflow and organize system prompt into file

Author: E-Kuerschner

.github/workflows/bug-reproduction-instructions.yml

@@ -8,7 +8,7 @@
 name: Bug Report Reproduction Check
 on:
   issues:
-    types: [opened, labeled]
+    types: [labeled]
 
 permissions:
   contents: read
@@ -39,11 +39,7 @@ jobs:
         uses: actions/ai-inference@v1
         with:
           model: mistral-ai/ministral-3b
-          system-prompt: |
-            Given a bug report title and text for a web application, return 'pass' if there is enough information to reliably reproduce the issue, 
-            meaning the report clearly describes the steps to reproduce the problem, specifies the expected and actual behavior, and includes environment details such as browser and operating system; 
-            if any of these elements are missing or unclear, return a brief description of what is missing in a friendly response to the author instead of 'pass'. 
-            Consider the following title and body:
+          system-prompt-file: './.github/workflows/prompts/bug-reproduction-requirements.txt'
           prompt: |
             Title: ${{ steps.issue.outputs.title }}
             Body: ${{ steps.issue.outputs.body }}
@@ -52,7 +48,7 @@ jobs:
         if: contains(join(github.event.issue.labels.*.name, ','), 'bug') && steps.analyze-issue.outputs.response != 'pass'
         uses: actions/github-script@v7
         env:
-          AI_RESPONSE: steps.analyze-issue.outputs.response
+          AI_RESPONSE: ${{ steps.analyze-issue.outputs.response }}
         with:
           script: |
             const issue_number = context.issue.number

.github/workflows/prompts/bug-reproduction-requirements.txt

@@ -0,0 +1,9 @@
+Given a bug report title and description for a custom React hook NPM module, return 'pass' if there is enough information to reliably reproduce the issue.
+A passing bug report must meet these criteria:
+1. A clear description of the bug; "it doesn't work" or something similarly vague is not acceptable
+2. A clear description of the expected behavior; "it should work" or something similarly vague is not acceptable
+3. Environment details containing at least the React version number, the version number of the library and the browser/runtime the user's application is running on
+
+If any of these elements are missing or unclear, return a brief description of what is missing in a friendly response to the author instead of 'pass'.
+
+Consider the following title and body: