ArchPilot reviews only the code you changed, comments on the exact line, explains why and suggests the fix. Existing debt stays out of your PR, and a comment you fix closes itself.
Screens from a running installation
Six situations that come up again and again in this role, and what AppArch does about each one.
The pipeline is green, every semicolon is in place, and the controller still talks straight to the database.
AppArch looks at the relationships between modules: the UI calling the database directly, the skipped layer, the circular dependency. Not the missing semicolon.
ArchScanA comment that only says something is wrong leaves you guessing what right looks like, and the review goes into a third round.
Every ArchPilot comment carries the reasoning and a suggested fix, in your workspace's language, English or Turkish. Disagree? Reply in the thread: the tone is a colleague's, not a bot's.
ArchPilotPush a typo fix and the bot posts the same twelve comments again. By Thursday nobody reads them.
Findings are keyed, so the same one is never posted twice, and the comment on a violation you fixed resolves itself. Your merge request stays clean and you get back to the code.
ArchPilotTouch a legacy file and the tool reviews all of it, as if you had written every line this morning.
ArchPilot reviews only the lines your merge request changes. The old debt is still tracked, in ArchScan's report where it belongs, not in your review.
ArchPilotThe tool is wrong about one case, and says so again on every run until people stop reading anything it says.
A workspace admin can close a finding as a false positive, an accepted risk or won't fix, with a reason. It stays closed on later runs, and the record keeps who closed it and why.
ArchScan"Violates the layering principle." Which principle, why does it matter here, and what should the code look like instead?
Every one of the 1000+ rules in the catalogue has its own documentation page explaining the reasoning, one click from the comment. The Arch handbook explains the patterns behind them.
Arch handbook
Ask for a PoC licence and try it on your own code, on your own servers.
New modules, release notes and writing on architecture. Leave with one click whenever you like.
