submit-changes

"PR" below means MR on GitLab, and "base" means target branch. Use the host's own terms when talking to the user and in the text you write.

Principle

Detect every value. Sources, highest precedence first:

1. Instructions: the repo's agent docs (AGENTS.md, CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, .cursor/rules/, CONTRIBUTING.md), then the user's own instructions and saved preferences, in whatever form the agent has them. Repo docs win on conflict; they describe the team.
2. The repo itself: PR templates, recent PRs, branch and commit history.
3. Fallbacks listed in each step.

When a source has a convention, follow it. When none does, use the fallback and say so in the confirmation step.

Attribution line. If the agent is set up to add an attribution line to PR bodies (a "Generated with ..." footer), it ranks below all three sources above. Detected the same way as the rest of §1 (see Attribution convention below).

In any agent