Menu
Run all preflight checks (format, gn_check, presubmit, build, tests) to make sure the current work is ready for review.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a Plaster (`rewrite/*.yaml`) config for an existing Brave-core Chromium `.patch`, authoring an intent-conveying regex match per the Plaster Dos and Don'ts, then verifying it by running `plaster.py apply` and diffing the regenerated patch against the original. Does not modify sources or create other files. Triggers on: plaster from patch, convert patch to plaster, plasterize, make a plaster.
For an external contributor's open PRs to brave/brave-core, ensure the `sync-and-rebase-pr-from-fork.yml` workflow has been dispatched for each PR's latest commit SHA — so a `contributor-*` draft PR exists inside brave/brave-core and CI can run. Invoke when the user says something like "create contributor PRs for <user>", "sync contributor PRs <list>", "run the rebase-from-fork workflow for these PRs", or passes a GitHub username / list of PR URLs/numbers.
Add a new best practice to the appropriate doc. Checks for duplicates, assigns stable IDs, creates new category docs if needed. Triggers on: add best practice, new best practice, add bp, new bp.
"Create an uplift PR that cherry-picks merged PRs from a contributor into a target branch (beta or release). Defaults to broad eligibility; the scope can be narrowed via a free-form description (e.g. 'only automated test and crash fixes'). Triggers on: /uplift, create uplift, uplift PRs."
Review PRs in the configured PR repository for best practices violations. Supports single PR (#12345), state filter (open/closed/all), and auto mode for cron. Triggers on: review prs, review recent prs, /review-prs, check prs for best practices.
Check if a failing test is a known upstream flake in Chromium's LUCI Analysis database. Provides flakiness statistics, verdict, and recommendation for filter file decisions. Triggers on: check upstream flake, is this test flaky upstream, check luci flakiness, upstream flake check.
| name | preflight |
| description | Run all preflight checks (format, gn_check, presubmit, build, tests) to make sure the current work is ready for review. |
| disable-model-invocation | true |
Run all preflight checks to make sure the current work is ready for review. Execute each step sequentially and stop immediately if any step fails.
all — Run all test suites (brave_browser_tests, brave_unit_tests,
brave_component_unittests) without filters, instead of only running tests
affected by the change. Usage: /preflight allgit branch --show-currentgit status --shortIf on master, create a new branch off of master before proceeding (use a
descriptive branch name based on the changes).
Run npm run format. If formatting changes any files, stage and include them in
the commit later.
Run npm run gn_check. Fix any issues found and re-run until it passes.
Skip this step if the only changes are to test filter files
(test/filters/*.filter) — filter files don't affect GN build configuration.
Run npm run presubmit. Fix any issues found and re-run until it passes.
Check git status. If there are any uncommitted changes (staged, unstaged, or
untracked files relevant to the work), create a commit. The commit message
should be short and succinct, describing what was done. If there are no changes,
skip this step.
Run npm run build to make sure the code builds. If it fails, fix the build
errors, amend the commit, and retry.
If work is targeting a different platform, follow the build instructions at README.md or confirm with the user which build arguments or technique to use.
If the all argument was provided: Run all test suites without filters:
npm run test -- brave_browser_testsnpm run test -- brave_unit_testsnpm run test -- brave_component_unittestsnpm run test-unitOtherwise (default): Determine which test suites are affected by the changes
in this branch (compare against master). Look at the changed files and
identify the corresponding test suites and relevant test filters.
npm run test -- [test suite] --filter="..."where test suite is any of:
Or npm run test-unit -- [path blob filter] to run jest for any
*.test.{ts,tsx} files.
If no tests are affected, note that and move on.
If any step required fixes (build errors, test failures, format/lint issues), amend the commit with the fixes and re-run checks until everything passes cleanly.