From 2c9043d65f9be99b88d179e41100d3dcd13144c8 Mon Sep 17 00:00:00 2001
From: Mark Wylde <mark@wylde.net>
Date: Sat, 31 May 2025 13:46:05 +0100
Subject: [PATCH] fix: prompt

---
 src/create-prompt/index.ts | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/src/create-prompt/index.ts b/src/create-prompt/index.ts
index e2c5d16..7ee17ab 100644
--- a/src/create-prompt/index.ts
+++ b/src/create-prompt/index.ts
@@ -576,8 +576,8 @@ ${
       - Commit changes using mcp__local_git_ops__commit_files (works for both new and existing files)
       - 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
-    `
-            : `}
+          `
+            : `
       - IMPORTANT: You are currently on the base branch (${eventData.baseBranch}). Before making changes, you should first check if there's already an existing claude branch for this ${eventData.isPR ? "PR" : "issue"}.
       - FIRST: Use Bash to run \`git branch -r | grep "claude/${eventData.isPR ? "pr" : "issue"}-${eventData.isPR ? eventData.prNumber : eventData.issueNumber}"\` to check for existing branches.
       - If an existing claude branch is found:
@@ -591,7 +591,7 @@ ${
       - 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 should create a PR using mcp__local_git_ops__create_pull_request unless one already exists for that branch.
-      - When pushing changes and TRIGGER_USERNAME is not "Unknown", include a "Co-authored-by: ${context.triggerUsername} <${context.triggerUsername}@users.noreply.local>" line in the commit message.
+    `
       }
 
    C. For Complex Changes:
@@ -660,8 +660,7 @@ c. List key information from the provided data
 d. Outline the main tasks and potential challenges
 e. Propose a high-level plan of action, including any repo setup steps and linting/testing steps. Remember, you are on a fresh checkout of the branch, so you may need to install dependencies, run build commands, etc.
 f. If you are unable to complete certain steps, such as running a linter or test suite, particularly due to missing permissions, explain this in your comment so that the user can update your \`--allowedTools\`.
-`
-      }`;
+`;
 
   if (context.customInstructions) {
     promptContent += `\n\nCUSTOM INSTRUCTIONS:\n${context.customInstructions}`;