Use _ for dart skills lint package

tool/dart-skills-lint/.agents/skills/add-dart-lint-validation-rule/SKILL.md → tool/dart_skills_lint/.agents/skills/add-dart-lint-validation-rule/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: add-dart-lint-validation-rule
-description: Instructions for adding a new validation rule and CLI flag to dart-skills-lint.
+description: Instructions for adding a new validation rule and CLI flag to dart_skills_lint.
 ---
 
 # Add a New Validation Rule and Flag
@@ -100,21 +100,21 @@ test('triggers error when description does not end with period', () async {
     name: 'test-skill',
     description: 'This description does not end with a period',
   );
-  
+
   final validator = Validator(rules: {descriptionTrailingPeriodCheck});
   final result = await validator.validate(tempDir);
-  
+
   expect(result.validationErrors.any((e) => e.ruleId == 'description-trailing-period'), isTrue);
 });
 test('skips error when description ends with period', () async {
   final tempDir = createTempSkillDir(
     name: 'test-skill',
     description: 'This description ends with a period.',
   );
-  
+
   final validator = Validator(rules: {descriptionTrailingPeriodCheck});
   final result = await validator.validate(tempDir);
-  
+
   expect(result.validationErrors.any((e) => e.ruleId == 'description-trailing-period'), isFalse);
 });
 ```
@@ -125,10 +125,10 @@ test('skips error when description ends with period', () async {
 
 When a new rule is introduced, verify that you synchronize sibling markdown files!
 
-1.  **`README.md`:** 
+1.  **`README.md`:**
     *   Add your flag under the **Usage** and **Flags** sections so users know it exists.
     *   Add descriptive lines under **Specification Validation**.
-2.  **`documentation/knowledge/SPECIFICATION.md`:** 
+2.  **`documentation/knowledge/SPECIFICATION.md`:**
     *   If the rule implements standard specifications traits, add constraints parameters under Section 5.1 (Validation parameters).
 
 ---

tool/dart-skills-lint/documentation/feature_design_docs/PRODUCTION_READYNESS.md → tool/dart_skills_lint/documentation/feature_design_docs/PRODUCTION_READYNESS.md

@@ -1,7 +1,7 @@
 # Production Readiness Evaluation: `dart-skills-lint`
 
 ## Executive Summary
-`dart-skills-lint` is a well-structured Dart CLI tool designed to enforce the Agent Skills specification. It demonstrates solid engineering fundamentals, including a decoupled architecture, comprehensive testing, and adherence to Dart CLI best practices. However, while the core logic is robust, it lacks several critical "production-grade" features required for broad ecosystem adoption and enterprise-level CI/CD integration.
+`dart_skills_lint` is a well-structured Dart CLI tool designed to enforce the Agent Skills specification. It demonstrates solid engineering fundamentals, including a decoupled architecture, comprehensive testing, and adherence to Dart CLI best practices. However, while the core logic is robust, it lacks several critical "production-grade" features required for broad ecosystem adoption and enterprise-level CI/CD integration.
 
 **Current Status:** **Beta / Tooling Candidate**
 *Suitable for internal use by Dart-savvy teams, but not yet ready for a broad, multi-language developer audience.*
@@ -17,7 +17,7 @@
 - **Configuration:** Initial support for `dart_skills_lint.yaml` allows for some flexibility in rule enforcement (error vs. warning).
 
 ### 2. Required Features Missing (Gaps)
-- **Distribution & Portability:** 
+- **Distribution & Portability:**
     - No pre-compiled binaries. Users are forced to have a Dart SDK installed, which is a barrier for non-Dart developers (e.g., Python or JS agent creators).
     - Not yet published to `pub.dev`.
 - **Machine-Readable Output:** The tool only outputs human-readable logs. Production CI/CD pipelines often require JSON, SARIF, or JUnit XML formats for automated reporting and dashboarding.