[reidbaker-agent]

Update to skills_lint 0.5.3 and enable new configs for published skills.
Along the way we found that a skill was not being limited.

@reidbaker

Details

Updates the `skills_lint` dev dependency from `^0.5.1` to `^0.5.3` and turns on more checks in `skills_lint.yaml`:

• New in 0.5.3, for the published skills/ directory: pub-archive-includes-skill (reports a skill or linked file that dart pub publish would leave out) and check-relative-paths with within-skill: true (reports relative links that leave the skill directory). skills/ has only a README today, so these guard future skills.
• Also for skills/: published-skill-name, which checks the package:skills naming convention (added in 0.5.2).
• For all skills: check-absolute-paths and disallowed-field. Both rules already existed before 0.5.3. disallowed-field checks the SKILL.md frontmatter keys.
• Marks .agents/skills/pre-push-skill as internal (metadata: internal: true) and lists it under individual_skills with prevent-skills-sh-publishing, the same way as check-readiness.
• test/validate_skills_test.dart now checks expect(config.parsingErrors, isEmpty). The 0.5.3 CHANGELOG notes that validateSkills returns true even when config.parsingErrors is not empty, so a typo in skills_lint.yaml (for example, an unknown rule name) would otherwise pass the test.

This is a dev-only change: it touches a dev dependency, the lint config, a dev skill and a test, with no change to the published plugin. It needs the override: no versioning needed and override: no changelog needed labels, as #12684 (the previous skills_lint bump) used, because the version-check tool does not treat pubspec.yaml and skills_lint.yaml as dev-only paths.

No issue tracks this routine dependency update, so this PR does not link one.

I prepared this change with help from an AI agent and reviewed it.

Local checks, against skills_lint 0.5.3 from pub.dev: flutter test passes (including test/validate_skills_test.dart), dart run skills_lint exits 0, and the repo tool's format, analyze, license-check and publish-check report no issues. validate --check-for-missing-changes passes when given the two override labels above.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request updates the camera_android_camerax package's skills configuration and validation. It marks the pre-push-skill as internal, upgrades skills_lint to version 0.5.3, expands the lint rules in skills_lint.yaml, and adds a check in validate_skills_test.dart to verify that the configuration parses successfully. No review comments were provided, so there is no additional feedback.