check_boundaries
Define dependency rules and check them against the import graph. Returns violations with file paths.
What it does
Define dependency rules and check them against the indexed codebase:
[
{ "from": "src/tools", "cannot_import": ["src/cli"] },
{ "from": "src/api", "cannot_import": ["src/db"] }
]Returns all violations with file paths and import locations.
Why this matters
Every team has architecture rules. Almost none of them are automatically enforced. check_boundaries makes violations findable — and fixable — in a single call.
No native equivalent at this level of semantic precision.
Related tools
Benchmark note
This benchmark compares CodeSift against the closest practical native workflow an agent would use for the same task.
For some tools, that baseline is a direct shell equivalent such as rg or find.
For AST-aware, graph-aware, and LSP-backed tools, the baseline is a multi-step workflow rather than a strictly identical command.
Results should be read as agent-workflow comparisons: token cost, call count, and practical context efficiency.