What LS-Lint does well
Direct naming, regex substitutions and cardinality checks for files and folders.
Performance evidence under review
Extend naming checks with repository policy and agent feedback.
LS-Lint supports naming, regex and file or directory cardinality. Keep it when that policy is sufficient. Try Assura for an additional repository convention or useful repair workflow. Historical report: recorded version 0.4.1 · 2026-09-30 UTC. These measurements do not establish current performance or published-version availability.
Historical performance summary; not raw CLI output.
cold accepted fixtures 8 / 8 fastercold aggregate 1.31xwarm 2x target 8 / 8 metwarm aggregate 24.80xrecorded version 0.4.1recorded date 2026-09-30 UTCWhere Assura starts
The same repository-level naming and placement concerns, with an LS-Lint migration path.
Where Assura fits
Configured content conventions, local references and actionable feedback alongside native linters and tests.
Beyond filesystem operations
Assura can inspect language-agnostic concerns inside files, including line counts, document structure, frontmatter, links, and references.
Less repeated policy
Reusable rule fragments and inherited project structure reduce duplication when the same expectations apply across multiple paths.
Repair guidance for agents
Rule-specific findings carry path and policy context so an agent can understand the expected repair instead of parsing a generic failure.
Performance claims stay bounded
Historical cold one-shot comparisons and warm persistent-session results describe separate execution paths. Current claims require verified provenance and passing regression gates; a recorded version is not proof of a published release.
Continue