chore: claude-code to v0.0.24 (#3)

Adding --depth=1 to fetchs to save time for large repos

action.yml

@@ -113,7 +113,7 @@ runs:
     - name: Run Claude Code
       id: claude-code
       if: steps.prepare.outputs.contains_trigger == 'true'
-      uses: anthropics/claude-code-base-action@c8e31bd52d9a149b3f8309d7978c6edaa282688d # v0.0.8
+      uses: anthropics/claude-code-base-action@v0.0.24
       with:
         prompt_file: /tmp/claude-prompts/claude-prompt.txt
         allowed_tools: ${{ env.ALLOWED_TOOLS }}

src/create-prompt/index.ts

@@ -536,7 +536,7 @@ ${
     ? `
 4. Check for Existing Branch (for issues and closed PRs):
    - Before implementing changes, check if there's already a claude branch for this ${eventData.isPR ? "PR" : "issue"}.
-   - Use Bash to run \`git branch -r | grep "claude/${eventData.isPR ? "pr" : "issue"}-${eventData.isPR ? eventData.prNumber : eventData.issueNumber}"\` to search for existing branches.
+   - Use the mcp__gitea__list_branches tool to list branches.
    - If found, use mcp__local_git_ops__checkout_branch to switch to the existing branch (set fetch_remote=true).
    - If not found, you'll create a new branch when making changes (see Execute Actions section).
    - Mark this todo as complete by checking the box.
@@ -566,6 +566,7 @@ ${
         eventData.isPR && !eventData.claudeBranch
           ? `
       - Commit changes using mcp__local_git_ops__commit_files to the existing branch (works for both new and existing files).
+      - Make sure commits follow the same convention as other commits in the repository.
       - Use mcp__local_git_ops__commit_files to commit files atomically in a single commit (supports single or multiple files).
       - CRITICAL: After committing, you MUST push the branch to the remote repository using mcp__local_git_ops__push_branch
       - After pushing, you MUST create a PR using mcp__local_git_ops__create_pull_request.
@@ -574,6 +575,7 @@ ${
             ? `
       - You are already on the correct branch (${eventData.claudeBranch}). Do not create a new branch.
       - Commit changes using mcp__local_git_ops__commit_files (works for both new and existing files)
+      - Make sure commits follow the same convention as other commits in the repository.
       - Use mcp__local_git_ops__commit_files to commit files atomically in a single commit (supports single or multiple files).
       - CRITICAL: After committing, you MUST push the branch to the remote repository using mcp__local_git_ops__push_branch
           `

src/github/operations/branch.ts

@@ -52,7 +52,7 @@ export async function setupBranch(
       );
 
       // Check out the base branch and let Claude create branches as needed
-      await $`git fetch origin ${sourceBranch}`;
+      await $`git fetch origin --depth=1 ${sourceBranch}`;
       await $`git checkout ${sourceBranch}`;
       await $`git pull origin ${sourceBranch}`;
 
@@ -99,7 +99,7 @@ export async function setupBranch(
 
     // Ensure we have the latest version of the source branch
     console.log(`Fetching latest ${sourceBranch}...`);
-    await $`git fetch origin ${sourceBranch}`;
+    await $`git fetch origin --depth=1 ${sourceBranch}`;
 
     // Checkout the source branch
     console.log(`Checking out ${sourceBranch}...`);

src/github/utils/local-git.ts

@@ -85,7 +85,7 @@ export async function branchHasChanges(
  */
 export async function fetchBranch(branchName: string): Promise<boolean> {
   try {
-    await $`git fetch origin ${branchName}`;
+    await $`git fetch origin --depth=1 ${branchName}`;
     return true;
   } catch (error) {
     console.log(