Skip to content

AGENTS: enforce branch-first sessions and no direct main/base edits #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
NagyVikt merged 1 commit into from
Apr 11, 2026
Merged

AGENTS: enforce branch-first sessions and no direct main/base edits #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,9 @@ This AGENTS.md is the top-level operating contract for this repository.

- For cleanup/refactor/deslop work: write a cleanup plan first.
- Lock behavior with regression tests before cleanup edits when needed.
- Treat `main` and any currently checked-out base branch as read-only workspaces.
- Every new session must start by creating an isolated agent branch/worktree via `scripts/agent-branch-start.sh` before making edits.
- If edits are found on `main`/base by mistake, immediately move them to a dedicated agent branch/worktree before continuing.
- Prefer deletion over addition.
- Reuse existing patterns before introducing new abstractions.
- No new dependencies without explicit request.
Expand Down Expand Up @@ -87,6 +90,8 @@ OMX runtime state typically lives under `.omx/`:
- Before deleting/replacing code, each agent must read the latest session comments/handoffs first and confirm the target code is in their owned scope.
- If ownership is unclear or overlaps, stop that edit, post a blocker comment, and let the leader/integrator reassign scope.
- For git isolation, each agent must start on a dedicated branch via `scripts/agent-branch-start.sh "<task-or-plan>" "<agent-name>"`.
- Do not implement changes directly on `main` or other base branches; all edits must happen on dedicated agent branches/worktrees.
- If the current local branch already contains accidental edits, move them to an agent branch/worktree first, then continue implementation.
- Agent completion must use `scripts/agent-branch-finish.sh` (merge into `dev`, push, delete agent branch).

1. Explicit ownership before edits
Expand Down
Loading