Hi Mateusz,
I think that the best idea would be to devote some time to identifying edge cases during the backlog grooming meeting, and probably also the sprint planning meeting. A list of common edge cases is also a good idea - I think it should be a separate page on Confluence.
Probably the most common edge case, the easiest one to find is one that I mentioned in the "Test Strategy" document:
An edge case or negative testing will consist, in this example, in checking what happens when trying to save the form when one or more of the required fields are blank.
But of course, there are also more complex ones, as Sebastian mentioned, e.g. those concerning permissions - I agree that we probably sometimes overlook it, unfortunately. In my view, the edge cases concerning a given ticket should be included in its description, the way it used to be months ago, when ticket descriptions used to be much longer than they tend to be now - there used to be a separate section concerning the edge cases.