Today · Combined remediation
Combined remediation
Your queue can hold fourteen things at once, and until now it asked you to decide about them one at a time. Select several, press Combine, and RepoOps writes one ordered plan across them: what ships together, what ships first, and which pull request a person has to sign off rather than the robot merging it.
How to use it
- Open Today and find the queue card. Press Select several.
- Tick the rows you want. Up to twelve. The bar under the list keeps count and tells you what a combine costs.
- Press Combine. One model call, on the cheap tier, against the same daily cap the rest of RepoOps spends from.
- Copy the prompt and paste it into a fresh coding session.
What the plan does that a list does not
Pasting six findings under one heading gives an agent six unrelated tasks and a merge conflict. The plan does four things instead:
- Groups by what a change touches. Two findings whose fixes are the same edit in different files become one pull request, not two.
- Orders the groups. Anything the others build on lands first.
- Splits the human-gated work out. An authorization fix does not ride in a pull request that merges itself on green, so it gets its own, and the prompt says so in the text the agent will follow.
- Says what done means, per item. A check somebody can run, not a description.
It reuses work already done
When RepoOps has already scoped one of your selected findings into a build brief, that brief goes into the plan whole: its root cause, the files it names, and its done-means. Nothing writes a second version of a fix somebody already worked out, because two versions of the same fix disagree the moment one of them changes.
What it will refuse to do
- It declines per item. A finding that does not carry enough to write a real instruction from is named in a Left out list, with the reason, and it is named in the prompt too. It is never quietly turned into a plausible sentence.
- Nothing you picked can vanish. Every item you selected ends up either in a group or in the left-out list, by name.
- It will not show a cost it has not measured. Until this machine has metered a combine, the bar says so rather than printing a figure.
- Twelve at a time. A prompt over more than that is a document rather than a plan.
Where it runs, and what it costs
On your own machine, against your own key. The findings do not leave it. The call goes through the same action pipeline as everything else RepoOps spends on, so it reserves against your daily planner cap, it lands on the audit log, and a machine set to watch refuses it before a cent is spent.
Last updated