Usage
Running Analysis
Section titled “Running Analysis”- On save — With
arxo.analyzeOnSaveenabled (default), saving a file triggers analysis. Results appear in the Problems panel and in the Arxo sidebar. - On demand — Use the command Arxo: Analyze Project from the Command Palette (
Ctrl+Shift+P/Cmd+Shift+P) to run analysis when you want.
Sidebar Views
Section titled “Sidebar Views”Open the Arxo view in the sidebar to see:
- Metrics — Architecture metrics from the last run
- Policy Violations — List of all current violations with location and message
Use Arxo: Show Metrics to focus the Metrics view.
Problems Panel
Section titled “Problems Panel”Arxo diagnostics appear in the standard Problems panel (Ctrl+Shift+M / Cmd+Shift+M). You can click a violation to jump to the file and line.
Code Actions
Section titled “Code Actions”When the cursor is on a line with an Arxo diagnostic, you can use quick fixes (e.g. Show Metrics, Open arxo.yaml) from the lightbulb menu or via the Problems panel.
Dependency Graph
Section titled “Dependency Graph”Use Arxo: View Dependency Graph to open the interactive dependency graph webview (data is provided by the LSP).
Status Bar
Section titled “Status Bar”The status bar shows architecture health and violation count when a project is analyzed.
Troubleshooting
Section titled “Troubleshooting”- No analysis — Ensure
arxo.lsp.serverPathis set correctly and thatarxo-lspruns from the terminal. - Wrong config — Set
arxo.configPathif yourarxo.yamlis not in the workspace root. - Extension output — Open Output → select Arxo to see LSP and extension logs.
For more, see Troubleshooting.