The Lint Runner Tool
Run the project’s linters and return violations with file and line — so an agent’s changes meet your standards before a human ever sees them, and reviews stay focused on substance.
A suggestion isn’t a shipped change
An agent that can only propose code still leaves all the work to a human. To actually deliver, it needs a real, governed workspace where it can run code, edit files, test, and use Git — safely, and without touching anything you didn’t allow.
Read-only agents
Suggestions still require a human to run, test, and commit everything.
Unsafe execution
Running agent-generated code on real infrastructure is a security risk.
No verification
Without tests and builds, an agent can’t know its change works.
Ungoverned Git
Direct repo access with no policy or audit is a non-starter in the enterprise.
Lint Runner, without the risk
Capability
What it does
Check code style and catch issues before review.
it runs the project’s linters and returns style and quality violations with locations.
Assignable to any agent
How it works
Predictable, inspectable behavior
Designed to be reliable.
it detects or accepts the lint command and parses the output into structured findings, so an agent can auto-fix or address issues before opening a pull request.
Every call logged
Governance
Private, governed, on-premise
Runs inside your perimeter.
Execution runs in an isolated, on-premise sandbox scoped per tenant with full command and file audit logging, so an agent can do real work on your code without unsafe access or anything leaving your perimeter.
Per-tenant, logged
Parameters
The lint_runner tool accepts these inputs when an agent calls it. Required inputs are flagged.
default: . Optional Project directory.
default: false Optional Apply auto-fixes where the linter supports them.
How the Lint Runner tool works in practice
Lint Runner is a code execution & workspace tool you assign to a VDF AI agent. It runs the project’s linters and returns style and quality violations with locations. Its hallmarks — Lint, Style, Findings — let an agent rely on it as a dependable step in a larger task rather than a brittle one-off script.
Under the hood, it detects or accepts the lint command and parses the output into structured findings, so an agent can auto-fix or address issues before opening a pull request. Every call is scoped to the requesting tenant and written to an audit log, so the capability is safe to run inside a regulated, on-premise environment — the same governance model behind every VDF AI tool.
Teams reach for Lint Runner when they need to handle standards, auto-fix, and cleaner PRs. It rarely works alone — pair it with Test Runner, Build Runner, and Code Smell Detector to build a complete, governed workflow, then compose those steps into an on-premise VDF AI Network.
Where Lint Runner pays back
Standards
Ensure changes match the team’s style.
Auto-fix
Let the agent clean up trivial issues automatically.
Cleaner PRs
Keep review focused on logic, not formatting.
Quality gates
Block code that fails lint from merging.
Assigned to agents, orchestrated as networks
On VDF AI, an industry’s use cases map to agents, and you assign tools like this one to those agents. Compose multiple agents into a governed, on-premise network.
What changes after you assign it
Questions about the Lint Runner tool
What is the Lint Runner tool?
It runs the project’s linters and returns style and quality violations with locations. Assigned to a VDF AI agent, it runs under role-based policy with full audit logging so the capability is safe to use in production.
Can it fix issues automatically?
Yes. Set fix to true to apply the linter’s auto-fixes where supported.
What does it return?
Structured violations with file and line so an agent can address each one.
What inputs does the Lint Runner tool need?
It has no strictly required inputs, and optionally accepts command, path, and fix. Each parameter is validated when an agent calls the tool, and the full call is logged for audit.
Which tools pair well with Lint Runner?
Lint Runner is commonly assigned alongside Test Runner, Build Runner, and Code Smell Detector. On VDF AI you compose several tools and agents into a single governed, on-premise network.
Does it run on-premise?
Yes. Like every VDF AI tool, it can run on-premise or in your sovereign cloud, scoped per user and audit-logged, so your data never leaves your perimeter.
How do agents use it?
You assign the tool to an agent under a role-based policy; the agent calls it as one step in a task, and several agents and tools can be orchestrated together as a governed VDF AI Network.
Assign Lint Runner to these agents
These VDF AI agents can be assigned this tool. Open an agent to see the full toolkit it can run.
Tools that work well alongside this one
Where this tool delivers value
Put Lint Runner to work
See the Lint Runner tool assigned to an agent and orchestrated in a governed, on-premise network.