dart-doc-validation — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited dart-doc-validation (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when:
///) in Dart code.Do NOT apply this skill or refactor doc comments when:
pseudo-code, non-Dart language identifiers (e.g. `yaml, `json, ```bash,
compile as valid Dart.
- **Generated Code**: Files generated by tools (e.g. `*.g.dart`, `*.mocks.dart`,
`*.freezed.dart`) where comments are synthesized.
- **External Markdown Hyperlinks**: Text in square brackets followed by a link
target (e.g. `[External Guide](https://...)`), which is standard Markdown
hyperlink syntax rather than an unresolved Dart doc reference.
## Discovery
To find documentation issues:
### Missing Lint
Verify if the `comment_references` lint is enabled:
- **Target**: `analysis_options.yaml`
- **Search Query**: `comment_references`
### Automated Validation
Run the documentation generator to surface warnings:
- **Command**: `dart doc -o $(mktemp -d)`
- **Keywords to look for**: `warning:`, `unresolved doc reference`,
`undefined macro`
## 2. Best Practices
### Enable the doc validation lint
In your `analysis_options.yaml`, enable the `comment_references` lint.
linter: rules:
### Validating Documentation Locally
Use the `dart doc` command with a temporary output directory to validate
documentation comments without polluting the local project workspace.
This command parses all documentation comments and reports warnings such as:
- `warning: unresolved doc reference`
- `warning: undefined macro`
**Command to run:**
dart doc -o $(mktemp -d)
_This will work on Mac and Linux._
This ensures that the generated HTML files are stored in a temporary location
and don't clutter the package directory, while still surfacing all validation
warnings in the terminal output.
**Browsing the docs:**
Our docs use features designed to be run on a web server. If you want to browse
the generated docs locally, install the `dhttpd` package.
dart install dhttpd TMP_DIR=$(mktemp -d) && dart doc -o "$TMP_DIR" && dhttpd --path "$TMP_DIR"
_(Or use another HTTP server, such as `python3 -m http.server`.)_
### Fixing Common Warnings
- **Unresolved doc reference**: Ensure that any identifier wrapped in square
brackets (`[Identifier]`) correctly points to an existing class, method,
property, or parameter in the current scope or imported libraries.
- **Undefined macro**: If using `{@macro macro_name}`, ensure that the template
`{@template macro_name}` is defined in the same file or a file that is
imported and visible to the documentation generator.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.