メニュー
Finds common violations of the Android accessibility API in the Clank App Java code and attempts to address them (e.g. hardcoded state change announcements, missing events, focus moving, assertive live regions, etc).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | accessibility-cleanup |
| description | Finds common violations of the Android accessibility API in the Clank App Java code and attempts to address them (e.g. hardcoded state change announcements, missing events, focus moving, assertive live regions, etc). |
Identify and fix accessibility bugs in Android Java files where developers are inadvertently violating the expected contract of the Android accessibility API.
The Android Accessibility API has many subtle rules that have changed over time. Developers often write custom accessibility code based on the end user result when testing with TalkBack, but don't actually honor the API contract which would make the feature work with TalkBack and any other running assistive technology. The goal of this work is to identify these common issues and anti- patterns and proactively fix them in the code.
Goal: Identify common violations of the Android accessibility API and fix them in Clank Java files.
[!IMPORTANT] Execution Protocol: Execute all steps sequentially one by one. Do not skip any step. Do not use
edit-codeorgrep. Userg(ripgrep) for searches.
Follow the workspace preparation steps in workspace_preparation.md to ensure a clean and updated environment.
Follow the Discovery & Batch Selection workflow.
Process the candidates by handling them one file at a time, and applying modifications inside each file one instance at a time (rather than refactoring all files or instances at once). This ensures stability and allows for precise verification.
R.string.accessibility_expanded_group) are now unused. If they are,
remove them from the corresponding .grd / .grsp resource files.git cl format.git cl format to format the modified source
code. Address any errors that are reported.generalist sub-agent. Proceed to the
Verification phase only after the review returns PASS.Follow the Verification workflow.
<SourceFileName>
and <SourceFilePath> from the candidate.
Invoke the Submission workflow. Pass the following context variables to the workflow:
accessibility-cleanupcleanup-a11y-<ComponentName> (where ComponentName is the
class name of the candidate file)Accessibility CleanupImprove accessibility semantics in <SourceFileName><Write a concise description explaining the changes (what, why, how) for the commit message.>531299755<Bug ID> from the Bug Tracking step.<SourceFileName>1Identify and safely remove expired Chromium histograms (dead metrics/technical debt). Use this skill when a contributor asks to clean up metrics, fix code health issues related to histograms, remove obsolete code, or work on a histogram cleanup task.
Orchestrator for the "Code Health Hub" framework. Trigger only when the user refers to the Hub or asks to see "available cleanup tasks" within the Chromium technical debt reduction system.
Identify and clean up inline fully qualified Java names (FQNs) in first-party code, replacing them with standard imports.
Add missing LINT.IfChange(...) / LINT.ThenChange(...) guards to enums in C++/Java and XML to keep them in sync. Trigger this skill ONLY when a contributor explicitly asks to add lint guards or synchronize enums using LINT guards.