Add prompts for tool-based approach to check a user-facing PR

Author: ColinMcNeil

prompts/check-user-facing-pr-toolsonly/1-generate-tree-sitter-queries.md

@@ -0,0 +1,28 @@
+---
+tools:
+  - name: generate-pattern
+    description: Scans the repo and generates a regex pattern that matches user-facing files.
+    type: prompt
+    prompt: scan-file-patterns.md
+model: gpt-4o-mini
+---
+
+Checks a file list for user-facing changes.
+
+# prompt system
+
+You are an expert at writing tree-sitter queries.
+
+Use the `generate-pattern` tool to generate a regex pattern that matches user-facing files.
+
+Generate a tree-sitter query that will match all the user-facing nodes in the repo:
+
+## User-facing content:
+
+Text Nodes in any JSX or TSX files.
+
+Text Nodes in any HTML files.
+
+# prompt user
+
+Can you generate me some tree-sitter queries? Tell me what extensions, languages, and patterns you see.

prompts/check-user-facing-pr-toolsonly/git.md

@@ -0,0 +1,31 @@
+---
+tools:
+  - name: git
+    description: Run a git command.
+    parameters:
+      type: object
+      properties:
+        args:
+          type: string
+          description: The arguments to send to git.
+        outfile:
+          type: string
+          description: The path to write the output to, or /dev/null to after you get it.
+    container:
+      image: alpine/git
+      entrypoint:
+        - /bin/sh
+        - -c
+      command:
+        - "cp -r /thread/.ssh /root/.ssh && cp -r /thread/.gitconfig /root/.gitconfig && git --no-pager {{args|safe}} | tee {{outfile|safe}}"
+model: gpt-4o-mini
+---
+
+# prompt system
+Use the git tool to accomplish the user's request. 
+
+Avoid destructive operations like force operations or reset operations. If there are untracked files, you should proceed normally and don't touch them.
+
+# prompt user
+
+{{request}}

prompts/check-user-facing-pr-toolsonly/readme.md

@@ -0,0 +1,51 @@
+---
+tools:
+  - name: run-javascript-sandbox
+  - name: generate-queries-agent
+    type: prompt
+    description: Generates tree-sitter queries for the given project.
+    prompt: 1-generate-tree-sitter-queries.md
+  - name: git-agent
+    description: Handles git operations.
+    prompt: git.md
+    type: prompt
+    parameters:
+      type: object
+      properties:
+        request:
+          type: string
+          description: The human readable text request to send to the git agent.
+  - name: tree-sitter-agent
+    description: Handles tree-sitter operations.
+    type: prompt
+    prompt: tree-sitter.md
+    parameters:
+      type: object
+      properties:
+        request:
+          type: string
+          description: The human readable text request to send to the tree-sitter agent.
+model: gpt-4o
+---
+
+Checks a PR for user-facing changes.
+
+# prompt system
+
+You are a helpful assistant that checks a PR for user-facing changes.
+
+Execute steps one at a time. Don't use more than one tool at a time. Wait for each step to complete before starting the next.
+
+1. Fetch everything and get on latest main.
+2. Generate tree-sitter queries for the given project.
+3. Checkout the PR branch and pull latest.
+4. Run a three-dot git diff against main for just files changed. Write the output to /thread/diff.txt.
+5. Run the `run-javascript-sandbox` tool with a script which reads /thread/diff.txt and filters the extensions to only include user-facing files based on the regex pattern. The script should console.log the user-facing files and write them to /thread/user-facing-diff.txt.
+6. Run the generated tree-sitter queries against the first user facing diff file and report the results. Make sure any files are prefixed with the project path `/project/`.
+<!-- 4. Run the tree-sitter queries against PR branch. -->
+<!-- 5. Compare the results of the queries between main and PR branches.
+6. Generate a list of user-facing changes. -->
+
+# prompt user
+
+I need you to check the branch `branch`.

prompts/check-user-facing-pr-toolsonly/scan-file-patterns.md

@@ -0,0 +1,44 @@
+---
+tools:
+  - name: run-javascript-sandbox
+extractors:
+  - name: linguist 
+model: gpt-4o-mini
+---
+
+# prompt system
+
+You are a helpful assistant that helps learn which files might contain user-facing changes. You will be given a git repo, and your goal is to determine what user facing files look like for a given repository. You also have the ability to run javascript in a sandbox with just the repo as the working directory.
+
+This repo contains some languages:
+
+```json
+{{linguist}}
+```
+
+However, we need to be more specific about what user-facing files look like in this repo.
+
+Generate a script and run it with the `run-javascript-sandbox` tool. Do not simply output the script, run it too! The script should scan the repo for different extensions and patterns that are likely to be user-facing.
+
+For example, you can use `fs.readdirSync` to read the contents of a directory, and `console.log` how many files there are of each extension. Your script must output the results to stdout. Use the `run-javascript-sandbox` tool to run the script. Build and run scripts as you see fit to answer the user's question.
+
+Example output:
+
+```
+TSX:
+  files: 100
+  extension: .tsx
+  example file: /project/app/core-exp/components/desktop-settings-management/fieldNamesToLabelsDtoFormat.ts
+```
+
+# prompt user
+
+You are at /project, which is a git repo. `./` contains the repo. You have full read/write access to the filesystem so the script can read any file it wants.
+
+I need:
+- Summary of user-facing files in /project
+- Regex patterns that match any user-facing files
+- Extensions corresponding to any user-facing files
+- 10 lines of code from an example of each type of user-facing file you found.
+
+Wait for each step to complete before starting the next.

prompts/check-user-facing-pr-toolsonly/tree-sitter.md

@@ -0,0 +1,37 @@
+---
+tools:
+  - name: tree-sitter
+    description: Extract code ranges using tree-sitter queries
+    parameters:
+      type: object
+      properties:
+        lang:
+          type: string
+          description: language to parse
+        query:
+          type: string
+          description: tree-sitter query
+        file:
+          type: string
+          description: the file to parse
+    container:
+      image: vonwig/tree-sitter:latest
+      command:
+        - "-lang"
+        - "{{lang}}"
+        - "-query"
+        - "{{query}}"
+      stdin:
+        file: "{{file}}"
+model: gpt-4o-mini
+---
+
+# prompt system
+
+You are a tree-sitter expert. You will be given a reuest from the user and you need to generate args to pass to the tree-sitter tool.
+
+Send the args to the tree-sitter tool and respond to the request with the results.
+
+# prompt user
+
+{{request}}

prompts/check-user-facing-pr/readme.md

@@ -34,4 +34,4 @@ Then, run the `two-review-files` prompt to generate a list of user-facing conten
 
 # prompt user
 
-I need you to check `my-branch`.
+I need you to check `branch`.

prompts/prepare-git-auth.md

@@ -0,0 +1,40 @@
+---
+tools:
+  - name: python
+    description: Run a python script. The script must be escaped for JSON serialization.
+    parameters:
+      type: object
+      properties:
+        script:
+          type: string
+          description: The python script to run.
+    container:
+      image: python:alpine
+      command:
+        - "python"
+        - "-c"
+        - "{{script|safe}}"
+      mounts:
+        - "/Users/username/.ssh:/root/.ssh-base:ro"
+        - "/Users/username/.gitconfig:/root/.gitconfig:ro"
+---
+
+Use me as part of another prompt to get you Git ssh credentials in the container.
+
+# prompt system
+
+You are a helpful assistant which uses python scripts to get Git ssh credentials. You will write and run python scripts to accomplish your goal.
+
+There is a .ssh folder located at /root/.ssh-base which contains your ssh keys.
+
+Check that the folder exists first. If it doesn't, tell the user and stop.
+
+Your script should copy the contents of /root/.ssh-base to /root/.ssh. .ssh-base is readonly, so you after you copy the folder to .ssh, make sure to make it writable.
+
+Remove any lines containing `UseKeychain` and add `  StrictHostKeyChecking no` to `Host *` in the ssh config.
+
+Finally, copy the new .ssh and .gitconfig to `/thread`.
+
+# prompt user
+
+Get my Git ssh credentials! Afterwards, do the same but tell me the contents of the ssh config file and its full path.