From 8f6cda006cf2e6968d53ce416d0c3ceb56fa449d Mon Sep 17 00:00:00 2001
From: Chris Samuel <csamuel@gmail.com>
Date: Tue, 21 Oct 2025 07:47:44 -0500
Subject: [PATCH] chore: add CLAUDE.md symlink, tune workflow prompts

---
 .github/workflows/claude-code-review.yml |  2 +-
 .github/workflows/claude.yml             | 16 +++++++++++++---
 CLAUDE.md                                |  1 +
 3 files changed, 15 insertions(+), 4 deletions(-)
 create mode 120000 CLAUDE.md

diff --git a/.github/workflows/claude-code-review.yml b/.github/workflows/claude-code-review.yml
index b6eacf0..606321f 100644
--- a/.github/workflows/claude-code-review.yml
+++ b/.github/workflows/claude-code-review.yml
@@ -39,7 +39,7 @@ jobs:
             - Security concerns
             - Test coverage
 
-            Use the repository's AGENTS.md for guidance on style and conventions. Be constructive and helpful in your feedback.
+            Use the repository's CLAUDE.md for guidance on style and conventions. Be constructive and helpful in your feedback.
 
             Use `gh pr comment` with your Bash tool to leave your review as a comment on the PR.
 
diff --git a/.github/workflows/claude.yml b/.github/workflows/claude.yml
index 26bfe17..3b21627 100644
--- a/.github/workflows/claude.yml
+++ b/.github/workflows/claude.yml
@@ -50,12 +50,22 @@ jobs:
 
             When working on this codebase:
 
-            - Use the repository's AGENTS.md for guidance on style and conventions.
+            - Use the repository's CLAUDE.md for guidance on style and conventions.
             - Maintain consistency with existing Nix style and patterns
             - Test any Nix changes for syntax validity
             - Keep configurations modular and well-documented
             - Follow the existing directory structure
 
+            **CRITICAL:** If the user is requesting a review or re-review of a PR, 
+              - Please provide feedback on:
+                - Code quality and best practices
+                - Potential bugs or issues
+                - Performance considerations
+                - Security concerns
+                - Test coverage
+              - Use inline comments on specific lines when providing feedback about particular code issues.
+              - For general comments or summary feedback, use `gh pr comment` or `gh issue comment` as appropriate. 
+
             ${{
               github.event_name == 'issue_comment' && format('ISSUE TITLE: {0}\n\nISSUE BODY:\n{1}\n\nCOMMENT:\n{2}', github.event.issue.title, github.event.issue.body, github.event.comment.body) ||
               github.event_name == 'pull_request_review_comment' && format('PR TITLE: {0}\n\nCOMMENT:\n{1}', github.event.pull_request.title, github.event.comment.body) ||
@@ -64,7 +74,7 @@ jobs:
             }}
 
           # Allow Claude to use necessary tools for managing this repository
-          claude_args: | 
-            --allowed-tools Bash,Read,Write,Edit,Glob,Grep
+          claude_args: |
+            --allowed-tools "Bash,Read,Write,Edit,Glob,Grep,mcp__github_inline_comment__create_inline_comment,Bash(gh issue view:*),Bash(gh search:*),Bash(gh issue list:*),Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*),Bash(gh pr list:*)"
             --model claude-sonnet-4-5-20250929
 
diff --git a/CLAUDE.md b/CLAUDE.md
new file mode 120000
index 0000000..47dc3e3
--- /dev/null
+++ b/CLAUDE.md
@@ -0,0 +1 @@
+AGENTS.md
\ No newline at end of file