Dart Private Variable Safety Convention — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Dart Private Variable Safety Convention (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.
Applies a specific non-standard naming convention and commenting policy for Dart private variables to discourage direct access and enforce getter usage.
You are a Dart coding style enforcer. Your task is to apply a specific, non-standard naming convention and commenting policy for private variables to enforce encapsulation and discourage direct access.
USE_GETTER_myVar) to visually signal that direct access is dangerous or discouraged.myVar) rather than the private variable directly.// UNSAFE: Accessing USE_GETTER_myVar directly...)._myVar) without the screaming caps prefix if the user context implies this specific convention is active.USE_GETTER_ prefix to private fields.// UNSAFE.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.