Two green tickets can still disagree
A textual conflict means Git cannot combine changes. A semantic conflict means the requested behaviors are incompatible, even when rebase succeeds and tests pass. Worktrees isolate working files; they do not prove that intentions are compatible.
For example, ticket A requires denying a discount to free accounts; ticket B requires making it available to everyone. Both suites may stay green if they cover different paths. Define the shared rule and test the same case, rather than only resolving the diff.
Prequalify and order related work
Prequalification examines active tickets and can identify functional dependencies. When overlap requires ordering, A becomes a prerequisite for B: B waits for A to finish and integrate before working on a base containing its result. Editing the same file alone does not necessarily require this dependency.
A broad request can be split into child tickets. Independent work runs in parallel; dependencies order the rest. The parent then verifies the combined result. This analysis reduces collisions but does not guarantee that every business contradiction will be detected.
Verify the integrated version
The agent commits in its worktree with the project’s hooks enabled. The integration queue serializes tickets for the same project; commits are rebased onto the latest base branch. If the base advanced, the agent must rerun affected tests and project checks, then inspect tests added or modified by other tickets. A clean rebase is insufficient.
Hooks run only the configured checks: a formatting hook does not validate a business rule. Integration and end-to-end tests should cover interactions between features alongside unit tests.
What still needs a decision
Green tests do not guarantee the absence of semantic conflicts. An expectation missing from tests can go unnoticed. Contradictory requests require explicit acceptance criteria and a decision about the intended rule before integration; human review remains useful for that decision. Turning off auto-merge keeps the result in the Review tab.
When preparing a ticket, name the shared function, identify related tickets, and specify the common rule and a regression example. Message count per ticket is neither a quality guarantee nor a promise to eliminate all review.
See the worktree and integration guide, orchestration documentation, and the article on dependencies and parent tickets.