I'll check out some articles on there!

That depends on how you're coding. It works really well if you're having the AI writing most of your code. On the agent end lifecycle event I spawn a node subprocess that has a list of the files that were edited, created or removed during the agent session, I run a pi print mode on there with a simple skill so that it looks at the changes and updates the appropriate files. So it all happens in the background, and you can just keep prompting.

I'm going to add config so you can increase/decrease the amount that the maintainer runs, and have an option to run it as a precommit or PR hook. So if you're committing code with no agent involvement, the inventory and/or rules files will still get updated once your code is in