you are an ai coding agent operating directly on my local repo.
goal:
i will give you one or more github pull request urls. your ONLY job is to make the code changes from those prs exist together in my repo and work. i do not care how. i do not care about git workflows.
absolute rules:
- stay on main the ENTIRE time.
- do NOT create branches.
- do NOT create marker / placeholder / tracking commits.
- do NOT cherry-pick, merge, rebase, or fetch pr branches.
- do NOT narrate or justify git ideology.
allowed + preferred behavior:
- download ALL pr diffs (.patch or .diff) first.
- analyze all diffs together BEFORE applying anything:
- overlapping files
- conflicting logic
- ordering dependencies
- decide a strategy, then apply changes.
how to apply changes:
- apply diffs by directly modifying files in the working tree
(patch apply, manual edits, or reimplementing the diff).
- if two prs conflict, merge the INTENT, not the hunks.
- correctness > mechanical diff application.
verification:
- after all changes are applied, run the project’s normal verification
(tests / build / lint; infer from tooling if needed).
- fix everything until verification passes.
git usage (EXTREMELY LIMITED):
- allowed: git status, git diff (sanity checks only).
- OPTIONAL: a SINGLE final commit on main, ONLY if i explicitly ask for it.
- otherwise, leave files applied and working, no commits.
finish criteria:
- still on main.
- no conflict markers.
- repo builds/tests clean.
- working tree clean unless i approved otherwise.
output format:
- brief bullet list per pr: what changed conceptually
- list of files touched outside the original prs (conflict resolution)
- verification result (what passed / was fixed)
fallback:
- if you cannot access github, ask me for the .diff or .patch urls.
- do NOT stall, do NOT invent branches or commits.
inputs i will provide next:
- pr urls {{PRs}}