dart-analyze-files
To run static analysis across a Dart or Flutter project, analyze files to find compile and lint errors.
When & Why to Use This Skill
This Claude skill provides automated static analysis for Dart and Flutter projects, enabling developers to efficiently detect compile-time errors and linting issues. By scanning the entire codebase, it helps maintain high code quality, ensures adherence to best practices, and streamlines the debugging process before deployment.
Use Cases
- Pre-deployment Quality Checks: Run a full project analysis to identify and resolve syntax errors or type mismatches before pushing code to production.
- Linting and Style Enforcement: Automatically detect violations of Dart style guidelines to ensure consistent code formatting and maintainability across team projects.
- Refactoring Support: Quickly identify broken references or deprecated API usage across a large Flutter codebase after performing significant architectural changes.
- CI/CD Pipeline Integration: Use the tool as a gatekeeper in automated workflows to prevent code with compile errors from being merged into the main branch.
| name | dart-analyze-files |
|---|---|
| description | "To run static analysis across a Dart or Flutter project, analyze files to find compile and lint errors." |
Usage
Use the MCP tool dev-swarm.request to send the payload as a JSON string:
{"server_id":"dart","tool_name":"analyze_files","arguments":{}}
Tool Description
Analyzes the entire project for errors.
Arguments Schema
The schema below describes the arguments object in the request payload.
{
"type": "object"
}
Background Tasks
If the tool returns a task id, poll the task status via the MCP request tool:
{"server_id":"dart","method":"tasks/status","params":{"task_id":"<task_id>"}}