How to roll, update, and integrate the skills_lint dependency into repositories (such as flutter/flutter). Use this skill when tasked with bumping skills_lint pinned commit refs in pubspec.yaml, configuring downstream test harnesses, managing package hashes, and generating submission pull requests. Do NOT use this skill for day-to-day skill validation or fixing skill markdown errors (use dart-skills-lint-validation instead).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
How to roll, update, and integrate the skills_lint dependency into repositories (such as flutter/flutter). Use this skill when tasked with bumping skills_lint pinned commit refs in pubspec.yaml, configuring downstream test harnesses, managing package hashes, and generating submission pull requests. Do NOT use this skill for day-to-day skill validation or fixing skill markdown errors (use dart-skills-lint-validation instead).
metadata
{"internal":true}
Integrating and Configuring skills_lint
Use this skill to verify repository state, update pinned references, manage
centralized configurations, implement efficient validation test suites, and
output clean pull request commands for skills_lint.
Pre-Flight Repository Verification
Before initiating any modifications or executing dependency updates, ensure
the repository is in a clean, safe state:
Run git status to confirm the repository has no active work in progress.
If clean, check out the primary tracking branch (e.g., main or master).
Fast-forward update from the remote owned by the authoritative org.
If post-checkout hooks report engine updates, run necessary sync utilities
(such as gclient sync) to guarantee consistency before proceeding.
Dependency Management Workflow
When updating skills_lint within a workspace or standalone project:
Locate the target pubspec.yaml defining the dependency.
Update the pinned Git commit reference directly in the ref field.
Synchronize the lockfile natively using the environment's package manager.
Configure rules and target paths globally via skills_lint.yaml. Always
define paths relative to the repository root execution context. Ensure that
rules at the directory level are properly oriented within a nested rules map.
To centralize rule management, load Configuration dynamically via
ConfigParser.loadConfig and supply it to validateSkills.
If test suites execute under simple environments with stable execution roots,
omit the skillDirPaths parameter entirely to natively inherit target paths
defined within the YAML configuration.
Absolute Isolation Pattern: If test harnesses manipulate runtime
execution working directories (such as CI frameworks running tests inside
sub-package folders), guarantee path resilience by resolving configuration
files absolutely using dynamic directory contexts (e.g., repoRoot.path).
Explicitly inject absolute skillDirPaths targeting; global rules defined
under rules: map unconditionally regardless of explicit target path usage.
When updating an existing validation block, explicitly audit any adjacent
TODO or tracker comments. If the comment describes refactoring config
loading or references issues resolved by this update, delete the comment
block entirely.
Core Validation Workflow
import 'package:path/path.dart' as path;
import 'package:skills_lint/skills_lint.dart';
const String _configFileName = 'skills_lint.yaml';
test('Validate Repository Skills', () async {
// Use dynamic absolute resolution references to guarantee CI stability
final Configuration config = await ConfigParser.loadConfig(
path: path.join(repoRoot.path, 'path', 'to', _configFileName),
);
expect(
config.directoryConfigs,
isNotEmpty,
reason: 'Configuration directoryConfigs should not be empty.',
);
final bool isValid = await validateSkills(
skillDirPaths: [skillsDirectory], // Explicit absolute targeting
config: config,
);
expect(isValid, isTrue);
});
Eliminating Duplicate Overhead in Secondary Blocks
Secondary test blocks enforcing specialized custom rules without loading the
shared configuration must supply target paths explicitly. To prevent
duplicate execution overhead, explicitly map all default registered
built-in rules to AnalysisSeverity.disabled.
Expected Final Output: Pull Request Creation Command
Conclude tasks by staging verified work on a descriptive local branch
(suffixed with the date in YYYY-MM-DD format), committing the changes with
a concise, standard commit message, and outputting a fully executable
gh pr create command.
Discovering and Populating the Pull Request Template
To ensure formatting compliance, always look up the target repository's native
pull request template before generating the submission body:
Locate Template: Search for template files within .github/,
.github/PULL_REQUEST_TEMPLATE/, or the project root. Common filenames
include PULL_REQUEST_TEMPLATE.md or pull_request_template.md.
Extract Structure: Read the discovered file to identify required
markdown headers, description placeholders, issue citation rules, and
checklists.
Populate Content: Replace placeholders with clear context summarizing
the dependency rolls, configurations created, and rule blocks optimized.
Check all applicable verification boxes ([x]).
Fallback: If no native template exists, construct a clean submission
body containing a brief summary of modifications, relevant issue links,
and static analysis/testing outcomes.
Output Command Structure
gh pr create \
--title "Update skills_lint dependency to <hash> and centralize config" \
--body "<populated repository template content>"
Tips for the Flutter Repository (flutter/flutter)
When operating directly within the main Flutter codebase:
Package Resolution: Run bin/flutter pub get at the repository root
instead of dart pub get to prevent SDK version mismatch errors.
Checksum Integrity: Updating dependencies natively breaks autogenerated
pubspec checksum hashes. Always recalculate and update stale hashes by
running bin/flutter update-packages --update-hashes.
Test Orchestration: Run repository unit tests from the root context:
bin/flutter test dev/tools/test/validate_skills_test.dart.
Verification: Ensure zero static analysis warnings using dart analyze --fatal-infos and format all source code cleanly with dart format.
