// Mandatory checks to run before completing any task that touches md files or dart code in this repository.
| name | definition-of-done |
| description | Mandatory checks to run before completing any task that touches md files or dart code in this repository. |
Use this skill to ensure that all work meets the repository standards before declaring a task complete or requesting review.
Before stating that a task is complete, you MUST execute and pass the following checks:
dart format . to format files, or dart format --output=none --set-exit-if-changed . to check without modifying. Ensure all files are formatted correctly.dart analyze --fatal-infos and ensure there are zero issues (including info-level issues).dart run dart_code_linter:metrics analyze lib and ensure there are zero issues. This checks for cyclomatic complexity and custom rules like file naming and redundant async.dart test and ensure all tests pass successfully.dart run dart_skills_lint -d .agents/skills to ensure they are valid.dart format . or checked with --output=none --set-exit-if-changed .).dart analyze --fatal-infos).dart run dart_code_linter:metrics analyze lib).dart test).dart run dart_skills_lint -d .agents/skills).How to integrate, update, and configure the dart_skills_lint validation tool within a repository. Make sure to use this skill whenever the user asks to update dart_skills_lint, configure skills validation tests, fix skills linter dependency drifts, verify repository state before editing, optimize lint rules execution, or draft pull request submission commands.
Contains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.
Use this skill when you need to set up validation for AI agent skills in a Dart project for the first time. This includes adding dependencies, configuring the linter, setting up tests, and creating a CI workflow.
Use this skill when you need to validate that AI agent skills meet the specification. This includes running the linter via CLI, authoring custom rules, and following the validation workflow.
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback. Use when you need to review code changes thoroughly.
Use the `http` package to execute GET, POST, PUT, or DELETE requests. Use when you need to fetch from or send data to a REST API.