Arcovia launched a few days ago and the response has been more useful than I expected. Instead of guessing what to build next, here's what real users have actually asked for, grouped by theme.
-
PR and branch comparison
Compare architecture health scores across git branches or PRs, so teams can see if a change improved things or introduced new hotspots before merging. Planned as a GitHub Action that comments on PRs with the score delta versus main.
Status: next up.
-
Custom architecture rules
A config file to define project-specific rules on top of the built-in ones, for example blocking src/components from importing src/server. Lets Arcovia fit the actual shape of a codebase instead of only default assumptions.
Status: scoping now. If you want this, comment with the kind of rules you'd need, import boundaries, coupling limits, file size, naming conventions.
-
Custom scoring weights
Let teams prioritize what matters most per project, security hotspots for a healthcare app versus duplication for a marketing site, instead of one fixed weighting for everyone.
Status: backlog, likely follows custom rules since they share the same configuration layer.
-
Suggested fixes for common patterns
Beyond flagging circular imports and hotspots, surface a suggested fix path for well-known patterns.
Status: exploring, no commitment yet.
If you're using Arcovia and have a specific need not listed here, comment below. Real usage is shaping this more than my own roadmap guesses.
Arcovia launched a few days ago and the response has been more useful than I expected. Instead of guessing what to build next, here's what real users have actually asked for, grouped by theme.
PR and branch comparison
Compare architecture health scores across git branches or PRs, so teams can see if a change improved things or introduced new hotspots before merging. Planned as a GitHub Action that comments on PRs with the score delta versus main.
Status: next up.
Custom architecture rules
A config file to define project-specific rules on top of the built-in ones, for example blocking src/components from importing src/server. Lets Arcovia fit the actual shape of a codebase instead of only default assumptions.
Status: scoping now. If you want this, comment with the kind of rules you'd need, import boundaries, coupling limits, file size, naming conventions.
Custom scoring weights
Let teams prioritize what matters most per project, security hotspots for a healthcare app versus duplication for a marketing site, instead of one fixed weighting for everyone.
Status: backlog, likely follows custom rules since they share the same configuration layer.
Suggested fixes for common patterns
Beyond flagging circular imports and hotspots, surface a suggested fix path for well-known patterns.
Status: exploring, no commitment yet.
If you're using Arcovia and have a specific need not listed here, comment below. Real usage is shaping this more than my own roadmap guesses.