Find areas that need attention
Surface product observations worth investigating before the next change.
GitMir reads the whole product and points at the things only somebody who read all of it would notice: a state nothing ever leaves, a record several things write and nothing reads, one idea living in two areas at once, an event raised that nothing listens for, a large area no described customer path goes through, the part absorbing most of the change. Each observation says what it is, what it costs to leave alone, and what would close it.
Open a project whose repository GitMir has read.
Read the list of places it says are worth a look, before you plan the next change.
Open any part it names to see what a change there would reach.
Write the ones you agree with down as work.
These follow from the structure of the product itself. They are not test failures, alerts or run-time data — GitMir never runs your code — and they are not feature suggestions. Observations about where a product is churning need more than one reading, so a freshly connected repository produces fewer of them. Seven kinds of observation exist today; you cannot add your own, and there is no way to mute one so it stops coming back.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.