This is a part of what we're working on at atomist - https://www.atomist.com/ https://www.atomist.com/ We're imagining the idea that your whole development flo

This is a part of what we're working on at atomist - https://www.atomist.com/ https://www.atomist.com/ We're imagining the idea that your whole development flow is expressible in terms of trees and expressions that we can use to navigate those trees. Say for example a webhook pushes a commit event. We can navigate from that commit, into the chat channel associated with it. Find the repo that contains it. Associate it with the build and link the two together in chat or, most relevant to this article, navigate into the code itself and perform an action such as changing the code or opening a PR with a suggested edit and comment. The interesting thing is that it's trees the whole way down. We can use the same expression to reach across all all kinds of events or to pick out individual tokens or structures inside the code. There's lots of information on our blog: https://the-composition.com/ https://the-composition.com/ We've open sourced a lot of our core work at: https://github.com/atomist https://github.com/atomist and are also interested in talking to teams about joining out alpha (see atomist.com) It's a really interesting problem to be working on.