Maestro

repowise 0.59 is out: 251 PRs in 4 days from 37 contributors, 26 of them first-timers. · guided setup for a new repo · a System Map of how your services call each other · Salesforce and COBOL, mapped end to end · agents record the decision each commit made pip install -U repowise Link: github.com/repowise-dev/repo…

Your agent says a function has zero callers and opens a PR to delete it. Before you merge, here are the 3 places a grep never looks and how to check each one:

Your agent says a function has zero callers and opens a PR to delete it. Before you merge, here are the 3 places a grep never looks and how to check each one:

Your agent says a function has zero callers and opens a PR to delete it. Before you merge, here are the 3 places a grep never looks and how to check each one:

If your agent waits for CI by re-reading the whole build log every time it checks, these are the 3 gh commands to give it instead.

Asked the agent to harden a function. Most of the diff guards against inputs that can't happen. Ask these 3 questions before you accept any of those guards:

If your agent opens every session by re-reading the same files it read yesterday, here are the 3 things to write down once so it stops paying for the same tour.

Your agent read a whole folder to answer a yes-or-no question about your repo. The 3 ways to phrase codebase questions so it opens the right file first:

Your agent's context is half full and it hasn't written a line yet. Open the transcript and read the first ten tool calls. They usually land in 3 kinds of file. Here is each one, and how to fence it off:

Your agent has been "almost done" for an hour and the token count keeps climbing. The 3 signals that it is looping, and what to do at each one: