ai: rename gemini code reviewer name

[2sem]

rename gemini code reviwer name from @gemini-cli to @gemini

[claude]

Pull Request Review: Rename Gemini Code Reviewer

Summary

This PR renames the Gemini code reviewer trigger from @gemini-cli to @gemini. The changes are focused and consistent across the workflow file.

---

✅ Code Quality & Best Practices

Positives:

• Consistent renaming: All 4 occurrences of @gemini-cli have been updated to @gemini
• Clean scope: The PR does exactly what it says - a simple rename with no scope creep
• Follows pattern: Aligns with the existing @claude naming convention in .github/workflows/claude.yml:16-19
• Documentation updated: Comments in the workflow file have been updated to reflect the new name (line 39)

Minor observation:

• The regex replacement logic at lines 88-89 is correct and properly updated

---

🐛 Potential Issues

No critical issues found, but consider:

1. Incomplete migration: The old @gemini-cli trigger will stop working immediately after this merge. If there are:

   • Existing documentation mentioning @gemini-cli
   • README files with usage examples
   • Team wiki or internal docs

   These should be updated in a follow-up PR or added to this one.

2. No deprecation period: Consider whether you want to support both @gemini-cli and @gemini temporarily with a deprecation warning. Currently the change is immediate and breaking for anyone using the old name.

---

⚡ Performance Considerations

No performance impact. The changes are string comparisons that execute identically.

---

🔒 Security Concerns

No security issues. The PR maintains the same security controls:

• ✅ Authorization check remains: OWNER/MEMBER/COLLABORATOR (line 47)
• ✅ Fork protection preserved: github.event.pull_request.head.repo.fork == false (line 43)
• ✅ User type validation: github.event.sender.type == 'User' (line 45)
• ✅ Permissions unchanged (lines 50-53)

---

🧪 Test Coverage

No tests provided, which is acceptable for this type of change, but consider:

1. Manual testing recommended:

   • Test that @gemini /review triggers the review workflow
   • Verify that @gemini-cli no longer works (expected)
   • Test on a PR comment, review comment, and new PR

2. Integration test opportunity: Consider adding a workflow test that validates the trigger patterns work correctly (though this may be overkill for a simple rename)

---

📝 Suggestions

1. Documentation: Update any README, CONTRIBUTING, or docs that reference the Gemini reviewer
2. Announcement: Consider notifying team members about the trigger name change
3. Commit message: The commit message "ai: rename gemini code reviewer name" is clear and follows convention

---

✨ Overall Assessment

Recommendation: ✅ APPROVE

This is a clean, focused PR that does exactly what it says. The implementation is correct and maintains all security controls. The only consideration is whether to update documentation and communicate the change to users.

Risk Level: Low
Complexity: Simple
Breaking Change: Yes (for users of @gemini-cli)

Great work keeping it simple and focused! 🚀

[2sem]

@gemini-cli /review

[2sem]

@gemini-cli /review this