open-webui-automation/tools
2
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Implement gitea_reviewer Role #13

New Issue
Open
opened 2026-01-17 13:36:04 +00:00 by xcaliber · 0 comments
xcaliber commented 2026-01-17 13:36:04 +00:00
Owner
Copy Link

Objective

Implement the gitea_reviewer role with PR diff analysis and pass/fail review logic.

Role Definition

gitea_reviewer → reads ticket, code, commits → comments on PR with pass/fail

Required Capabilities

  • Read PR diff and changed files
  • Read ticket requirements for validation
  • Read commit history for scope validation
  • Add inline comments on PR
  • Generate pass/fail review summary
  • Flag scope creep (code unrelated to ticket)
  • Validate commit message format

Review Checklist

  • Code matches ticket requirements
  • Commit messages follow format: {type}({scope}): {imperative description} Refs: #{issue-id}
  • No unrelated file modifications
  • Branch naming convention followed
  • Tests included for bug fixes

Technical Notes

  • Must detect scope creep (most common: code reduction removing unrelated functionality)
  • Must validate against 4K→30 lines anti-pattern
  • Bulk code removal requires explicit justification in PR

Dependencies

  • Requires Ticket #2 (gitea_coder) completion

Testing Criteria

  • Can detect mismatched ticket scope
  • Can validate commit message format
  • Can flag unrelated code changes
  • Can provide inline review comments
## Objective Implement the gitea_reviewer role with PR diff analysis and pass/fail review logic. ## Role Definition ``` gitea_reviewer → reads ticket, code, commits → comments on PR with pass/fail ``` ## Required Capabilities - [ ] Read PR diff and changed files - [ ] Read ticket requirements for validation - [ ] Read commit history for scope validation - [ ] Add inline comments on PR - [ ] Generate pass/fail review summary - [ ] Flag scope creep (code unrelated to ticket) - [ ] Validate commit message format ## Review Checklist - [ ] Code matches ticket requirements - [ ] Commit messages follow format: `{type}({scope}): {imperative description} Refs: #{issue-id}` - [ ] No unrelated file modifications - [ ] Branch naming convention followed - [ ] Tests included for bug fixes ## Technical Notes - Must detect scope creep (most common: code reduction removing unrelated functionality) - Must validate against 4K→30 lines anti-pattern - Bulk code removal requires explicit justification in PR ## Dependencies - Requires Ticket #2 (gitea_coder) completion ## Testing Criteria - Can detect mismatched ticket scope - Can validate commit message format - Can flag unrelated code changes - Can provide inline review comments
xcaliber added this to the Gitea Project Details for Role Refactoring project 2026-01-17 13:44:33 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project Gitea Project Details for Role Refactoring
Assignees
Clear assignees
c3jones3 xcaliber
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: open-webui-automation/tools#13
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?