Add Scope Enforcement to gitea_coder #12

New Issue

xcaliber · 2026-01-17T13:36:03Z

xcaliber commented

2026-01-17 13:36:03 +00:00

Objective

Add scope enforcement to gitea_coder to prevent the observed problems with LLMs sending deltas that wipe files clean.

Problem Statement

Even after renaming tools (update_file vs replace_file), LLMs still send deltas that wipe files nearly clean. Need process gating and explicit documentation.

Required Implementations

Enforce branch naming convention: {type}/{issue-id}-{short-description}
- Valid types: feature/, fix/, refactor/, docs/, test/
Prevent pushes to main branch
Ticket binding validation (commits must reference issue)
Full file mode documentation (explicitly state "Full Files w/ Changes Only")
Scope validation before branch creation

Technical Approach

Update function pydoc to explicitly state full file mode
Add scope checking before any file operations
Validate commit messages contain issue references
Reject operations that don't follow naming conventions

Testing Criteria

Branch creation fails without proper naming
Commits without issue references are rejected
Main branch receives no direct pushes
Scope creep is detected and blocked

## Objective Add scope enforcement to gitea_coder to prevent the observed problems with LLMs sending deltas that wipe files clean. ## Problem Statement Even after renaming tools (update_file vs replace_file), LLMs still send deltas that wipe files nearly clean. Need process gating and explicit documentation. ## Required Implementations - [ ] Enforce branch naming convention: `{type}/{issue-id}-{short-description}` - Valid types: feature/, fix/, refactor/, docs/, test/ - [ ] Prevent pushes to main branch - [ ] Ticket binding validation (commits must reference issue) - [ ] Full file mode documentation (explicitly state "Full Files w/ Changes Only") - [ ] Scope validation before branch creation ## Technical Approach - Update function pydoc to explicitly state full file mode - Add scope checking before any file operations - Validate commit messages contain issue references - Reject operations that don't follow naming conventions ## Testing Criteria - Branch creation fails without proper naming - Commits without issue references are rejected - Main branch receives no direct pushes - Scope creep is detected and blocked

xcaliber added this to the Gitea Project Details for Role Refactoring project 2026-01-17 13:44:33 +00:00

xcaliber closed this issue

2026-01-18 20:32:24 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: open-webui-automation/tools#12