Automatic re-test on mergeRe-test the issue when the fix merges.
Turn on re-test on merge and link a pull request to an issue. When the PR merges, Specurity waits the delay you set (and, if you add a health URL, until your app answers), then re-tests the issue.

How it worksThree steps from merge to verdict.
- 01
Link
Link a pull request to the issue, or put the issue key (e.g. PROJ-12) in the PR’s branch or title.
- 02
Wait
After the merge, Specurity waits the delay you set and, if you add a health URL, until your app answers.
- 03
Re-test
Escape AI re-tests the issue. If it no longer reproduces, it can close as Fixed; if the fix didn’t hold, it goes back to the team.
DetailsLet the re-test decide.
The re-test follows the merge.
Link a pull request to an issue, or mention the issue key (e.g. PROJ-12) in the PR’s branch or title. When the project re-tests on merge (it’s off until you turn it on), the merge starts the re-test, with no ticket to chase.
- Matched by link, or by the issue key in the branch or title
- Waits the delay you set: 5 minutes by default, up to 24 hours
- Add a health URL to wait until your app answers

See which fixes are proven, not just marked closed.
If the issue no longer reproduces, it can be closed as Fixed automatically (a project setting). If the re-test shows the fix didn’t hold, the issue goes back to the team, reopened if it was Fixed, and, by default, its assignees are told.
- One verdict: Reproduced, Not reproduced or Inconclusive
- Evidence and fix steps when the issue reproduces
- Assignees are told if the fix didn’t hold

FAQQuestions about re-testing on merge.
How do I verify that a security fix worked?
Re-test the issue. Start a re-test with Run on the issue, or turn on re-test on merge and link the fix’s pull request so the merge starts one. If the issue no longer reproduces, it can be closed as Fixed automatically (a project setting).
How soon after a merge does the re-test run?
Re-tests can start within minutes of the merge. Specurity waits the delay you set (5 minutes by default, up to 24 hours) and, if you add a health URL, until your app answers.
What happens if the fix doesn’t hold?
If the re-test shows the fix didn’t hold, the issue goes back to the team (reopened if it was Fixed) and, by default, its assignees are told. You also get the evidence, a proof-of-concept description, the impact and steps to fix.
Can I change the test cases before the next re-test?
Yes. Test cases are readable markdown written by your team. Read, edit or remove any before a re-test; the AI uses them as priority checks.
Start proving your fixesSee a real fix re-tested.
Talk to us, or apply for the pilot. Bring a recent pentest report if you have one.