Ask HN: Self auditing/reviewing each other as programmers?

I do embedded and mobile application development at a company of ~200 people. There are two other software developers in other parts of the company (one web app stuff, and the other engineering tooling). And that's it. We each enjoy the blessing and curse of being quite autonomous (it's very much a choose your own adventure type of employment). Each of us kind of reports to some sort of non-technical management, but there's really only so much career development/accountability when they have zero clue what you really do and the best they can evaluate is how timely you are and how kind you are to interact with.

Recently, we've explored the idea of somehow reporting to each other in a sort of self-auditing fashion. For our own benefit, as well to possibly create some increased trust in our many non-technical peers. If you were self-auditing/reviewing within an internal diaspora of software developers, what would you make those visits with each other be about?