// 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.
| name | code-health-hub |
| description | 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. |
Act as the Orchestrator for Chrome/Clank Code Healths. The goal is to make it frictionless for engineers to contribute outside their immediate area.
To maintain a fast and efficient session, MUST delegate heavy-lifting tasks to sub-agents:
generalist sub-agent. It is faster
and more reliable for high-volume text searches in Chromium using rg and
cs.codebase_investigator sub-agent.generalist sub-agent.generalist sub-agent to summarize output.By delegating, the main chat context remains lean.
Generic instructions for validation, bug tracking, and submission are available in:
When activated, immediately greet the user and use the ask_user tool to
present a menu of contribution categories.
Options to present:
If the user selects a category marked as (Coming soon), clearly inform them that this workflow is still under development and ask them to choose another option.
If the selection is Category A, use the ask_user tool again to prompt for a
specific Code Health task:
If the user selects an option marked as (Coming soon), clearly inform them that the skill is not yet available and ask them to choose another task.
For available tasks, do not instruct the user to activate the skill manually. Seamlessly transition into the selected skill's workflow by retrieving its instructions and immediately executing its initial steps:
activate_skill tool with
name="code-health-histogram-cleanup".Immediately begin executing the retrieved workflow without waiting for further user prompts.
ask_user tool for presenting menus to avoid manual typing from the
user. r.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.
Use when removing a `base::Feature` and its associated code
Guide for resolving NullAway static analysis errors. Best practices for: - Passing ObservableSupplier/Supplier<@Nullable T> - Dereferencing potentially @Nullable values - Adding @NullMarked to Java code
Identify 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.
How to identify and fix Java memory leaks in Android Chrome using LeakCanary traces.
Modularize a chrome/browser/ subfolder by splitting its sources out of the monolithic //chrome/browser:browser target into dedicated source_set targets in the subfolder's own BUILD.gn. Use when the user asks to modularize, extract, or create BUILD targets for a chrome/browser/ subfolder, or mentions "Project Bedrock", "//chrome/browser modularization", or wants to split a subfolder into header/impl/test targets. Also use when the user says "modularize chrome/browser/X" for any X.