fix: follow commit convention

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,10 +575,11 @@ ${
             ? `
       - 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
           `
-            : `}
+            : `
       - 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 +593,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 +662,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}`;