[camera_android_camerax] Migrate check-readiness skill from bash to Dart

[reidbaker]

1. Migrated check-readiness Skill to Dart

• Replaced scripts/check.sh with a Dart implementation.
• Implemented unit tests for the checker logic under test/check_test.dart

2. Tooling & CI Support for Agent Skills

• Static Analysis (Opt-in): Added a new --analyze-skills-for flag to the analyze command. When set, it explicitly runs dart analyze on the .agents/skills directories of the configured packages.
• CI Configuration: Configured the global analyze workflow in .ci/targets/analyze.yaml to run analysis on camera's skills via script/configs/skills_analysis.yaml.
• Unit Testing: Because .agents/skills/check-readiness is set up as a standalone Dart package with its own pubspec.yaml, the repository's existing dart-test command automatically discovers and runs its unit tests.
• Validation Exemption: Added .pubignore parsing support to RepositoryPackage and integrated it into the validate command. Any subpackage matching .pubignore patterns (e.g. .agents/skills/) is now skipped by the validate command, ensuring internal/contributor-only tools do not fail publishing hygiene checks.
• Versioning & CHANGELOG Exemption: Classified paths starting with .agents/ as developer-only changes. This exempts skill-only or script-only modifications within the .agents/ directory from triggering version-bump and CHANGELOG update requirements.

I asked my agent to articulate the interaction between top level packages tool commands and .agents/skills. Then I filtered the list to the command I thought reviewers or people looking at this pr later would find interesting.

Interaction of Packages Tool Commands with .agents/skills

Command	Targeting Scope	Runs on .agents/skills?	Interaction Details
analyze	topLevelOnly	Yes (Explicitly)	Runs pub get on the main package and all subpackages (including those in .agents/skills). If the main package is listed in --analyze-skills-for (configured in CI via script/configs/skills_analysis.yaml), it explicitly runs dart analyze --fatal-infos .agents/skills.
validate	includeAllSubpackages	No (Skipped)	Since .pubignore specifies .agents/, the skill packages are marked as ignored (isPubIgnored = true). The validate command skips them entirely (SKIPPING: Ignored by .pubignore), exempting developer-only helper tools from public-facing package hygiene rules.
dart-test	includeAllSubpackages	Yes	Because it targets all subpackages, it scans .agents/skills/*. If a skill package contains a test/ directory, it executes the Dart/Flutter unit tests inside it.
format	topLevelOnly	Yes	Uses recursive file gathering (getFilesForPackage) under the main package directory, formatting all Dart, C++, Java, Kotlin, and Swift files under .agents/skills/. It does not filter files using .pubignore.
license-check	N/A (Repository-wide)	Yes	Gathers all tracked files in Git via git ls-files. Any file checked into Git under .agents/skills/ is validated for standard first-party or recognized third-party license headers.
fix	includeAllSubpackages	Yes	Runs dart fix --apply inside any skill package directory that contains a pubspec.yaml.
update-dependency	includeAllSubpackages	Yes	If a targeted dependency is used by the skill package, its pubspec.yaml will be updated.
update-min-sdk	includeAllSubpackages	Yes	Updates SDK constraints inside the skill package's pubspec.yaml when run.
remove-dev-dependencies	includeAllSubpackages	Yes	Removes development dependencies from the skill package's pubspec.yaml when targeted.
publish-check	topLevelOnly	No	Runs on the main package. Because .agents/ is listed in .pubignore, the directory is excluded from the package archive and not uploaded or checked.
publish	topLevelOnly	No	Similar to publish-check, the .agents/ directory is skipped during publish due to .pubignore.
fetch-deps	topLevelOnly	No	N/A
list	N/A	No	Lists only top-level packages.

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 introduces a new local agent skill check-readiness to verify the environment, adds a custom lint rule to enforce that tracked skills are marked as internal, and implements proxy tests to run unit tests and validate skills. It also integrates several third-party skills via symlinks. The review feedback highlights several critical improvements: ensuring dependencies are resolved with pub get before running tests, avoiding crashes on broken symlinks by setting followLinks: false, adding safe type checks before casting YAML to a map, using Directory.current.path to robustly determine the workspace root, handling ProcessException when executing git commands, and updating the skill documentation to reference the Dart implementation instead of the duplicate bash script.

[gemini-code-assist]

Code Review

This pull request replaces the bash-based readiness check script with a Dart-based tool, introduces a new --analyze-skills-for flag to the analyze command, and adds support for skipping packages ignored by .pubignore during validation. The review feedback suggests enhancing the .pubignore matching logic to recursively check ancestor path segments for directory patterns without trailing slashes, adding corresponding test cases, and enabling followLinks: true when scanning for Dart files in .agents/skills to support symlinked directories.