Works with: Graphify (hosted), with a GitHub repository indexed in your workspace. No coding tools needed.
The scenario
A founder runs a product built mostly by coding agents and one freelance developer. Pull requests merge every day. The founder can’t tell whether the product is getting healthier or worse, and doesn’t want to approve changes blindly or slow everyone down by asking for explanations.What you’ll build
- A plain-language picture of how your product works, from the wiki.
- A short list of findings you’ve decided on, with a reason for each.
- A habit: decide once, record it, and let agents pick up the fix.
Before you start
- Your repository indexed in Graphify. See Quickstart.
- Reviews on for the repository. They are unless someone turned PR reviews off in Options on Repositories.
Setup
1
Learn how the product works
Open Wiki and choose a Repository. Select Ask about this project and start with “What does this project do? Explain it in plain language.” Each article shows a confidence label. Verified was read directly from the code, Inferred was worked out by analysis, and Needs review is a low-confidence guess to check with your developer.
2
See what needs attention
Open Insights. Under Sort, choose Highest priority (PRs). Under Priority, start with P0 · Critical and P1 · High. Under Evidence, Confirmed by test and Supported by code are the strongest. Not yet verified means nobody has checked the claim yet.
3
Ask until you understand
On a finding, select Ask about this finding and ask what you need, such as “What would a customer notice if this went wrong?” Answers come from the same graph and cite the code they used.
4
Decide, and say why
Set a Team decision: Open, Acknowledged, Fix proposed or Dismissed. Write a Reason and select Save team decision. Everyone in the workspace sees it.
5
Hand off the fix
Select Copy task for my agent and send the task to your developer or paste it into a coding agent. Use Preview or edit the task to add what matters to you. For the full loop, see Fix review findings with a coding agent.
6
Write down the rules you care about
When you decide something that should always hold, such as “Never email customers from a test environment”, add it in Memory and select Save and keep. Connected agents and Ask use kept memories. See Memory.
A weekly routine
How it works
Graphify builds a code knowledge graph of each repository and reviews pull requests against it. The wiki, Insights and Ask all read that graph, so every answer can point at the code behind it. Your team decisions and kept memories sit in the workspace, where developers and agents can see them. Graphify reviews don’t block a merge, and a Team decision doesn’t change the code. Someone still has to make the fix. What you get is a clear record of what you were told, what you decided and why.Verify it worked
- Findings you’ve decided on show your Team decision and Reason.
- A coding agent asked about a rule you saved in Memory quotes it back.
Troubleshooting
- Insights says “Code findings are not available for this workspace.” Insights isn’t turned on for your workspace. See Insights.
- A wiki article is marked Needs review. Ask your developer to check it against the code before you rely on it.
- There’s too much to read. Filter Priority to P0 · Critical only, and choose Repository one at a time.
Next steps
Try it in Graphify
We build and host the graph for you. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.
Insights
Every filter, status and decision.
Wiki
Read your codebase in plain language.