Enable use_commit_signing to provide MCP file ops server for CI fixes

- Add use_commit_signing: true to auto-fix workflows
- Update slash commands to use mcp__github_file_ops__commit_files
- This enables Claude to write and commit files through MCP

.claude/commands/fix-ci-commit.md

@@ -31,20 +31,18 @@ Based on the error logs:
 
 After fixing ALL issues, you MUST:
 
-```bash
+Use the `mcp__github_file_ops__commit_files` tool to commit all your changes with a descriptive message like:
-# Stage all changes
-git add -A
 
-# Commit with descriptive message
+```
-git commit -m "Fix CI failures
+Fix CI failures
 
 - Fixed syntax errors
 - Fixed formatting issues  
 - Fixed test failures
-[List actual fixes made]"
+[List actual fixes made]
 ```
 
-**IMPORTANT**: You MUST use the Bash tool to run the git add and git commit commands above. The workflow expects you to commit your changes.
+**IMPORTANT**: You MUST use the MCP file ops tool to commit your changes. The workflow expects you to commit your changes.
 
 ### 3. Verify (Optional)
 

.claude/commands/fix-ci.md

@@ -42,11 +42,11 @@ Requirements:
 
 ## Step 4: Commit Changes
 
-After applying ALL fixes, use the Bash tool to:
+After applying ALL fixes:
-1. Run: `git add -A` to stage all modified files
+1. Use the `mcp__github_file_ops__commit_files` tool to commit your changes
-2. Run: `git commit -m "Fix CI failures: <description>"` to commit the changes
+2. Include a descriptive commit message explaining what was fixed
-3. Include details about which CI jobs/tests were fixed in the commit message
+3. Document which CI jobs/tests were addressed in the commit message
-4. Important: You MUST use the Bash tool to run these git commands to commit your changes
+4. Important: Use the MCP file ops tool, not git commands directly
 
 ## Step 5: Verify Fixes Locally
 

.github/workflows/auto-fix-ci-inline.yml

@@ -147,6 +147,7 @@ jobs:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           timeout_minutes: "30"
           use_sticky_comment: "true"
+          use_commit_signing: "true"
           claude_args: "--max-turns 15"
 
       - name: Push fix branch

.github/workflows/auto-fix-ci.yml

@@ -89,6 +89,7 @@ jobs:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           timeout_minutes: "30"
           use_sticky_comment: "true"
+          use_commit_signing: "true"
           claude_args: "--max-turns 15"
 
       - name: Push fix branch

slash-commands/fix-ci-commit.md

@@ -31,20 +31,18 @@ Based on the error logs:
 
 After fixing ALL issues, you MUST:
 
-```bash
+Use the `mcp__github_file_ops__commit_files` tool to commit all your changes with a descriptive message like:
-# Stage all changes
-git add -A
 
-# Commit with descriptive message
+```
-git commit -m "Fix CI failures
+Fix CI failures
 
 - Fixed syntax errors
 - Fixed formatting issues  
 - Fixed test failures
-[List actual fixes made]"
+[List actual fixes made]
 ```
 
-**IMPORTANT**: You MUST use the Bash tool to run the git add and git commit commands above. The workflow expects you to commit your changes.
+**IMPORTANT**: You MUST use the MCP file ops tool to commit your changes. The workflow expects you to commit your changes.
 
 ### 3. Verify (Optional)
 

slash-commands/fix-ci.md

@@ -43,10 +43,10 @@ Requirements:
 ## Step 4: Commit Changes
 
 After applying fixes:
-1. Stage all modified files with `git add -A` or `git add .`
+1. Use the `mcp__github_file_ops__commit_files` tool to commit your changes
-2. Commit with a descriptive message using `git commit -m "Fix CI failures: <description>"`
+2. Include a descriptive commit message explaining what was fixed
-3. Include details about which CI jobs/tests were fixed in the commit message
+3. Document which CI jobs/tests were addressed in the commit message
-4. Important: Always commit your changes even if you're already on a branch
+4. Important: Use the MCP file ops tool to commit your changes
 
 ## Step 5: Verify Fixes Locally