// Guidance for local verification of changes to ensure they pass CI checks (linting, type checking, testing, and building).
How to add a new field to a feature across the entire stack (Data, API, and Frontend).
Guidance for working on the Flask-based backend, NDB Datastore, and OpenAPI integrations in chromium-dashboard.
Guidance for working on the Lit-based frontend, Shoelace widgets, and client-side routing in chromium-dashboard.
Guidance for running, debugging, and updating Playwright end-to-end tests in chromium-dashboard.
| name | chromestatus-ci-verification |
| description | Guidance for local verification of changes to ensure they pass CI checks (linting, type checking, testing, and building). |
This skill provides the necessary commands and context to verify your changes locally, matching the checks performed by the GitHub Actions CI pipeline in .github/workflows/ci.yml.
Before submitting a pull request, ensure all the following checks pass.
Ensure your local environment is correctly set up.
make setup
Runs Prettier, ESLint, and Lit-analyzer to check code style and common issues.
make lint
Runs mypy for static type analysis of Python code.
make mypy
Runs Python unit tests using the Datastore emulator.
npm test
Runs web component tests using Playwright.
make webtest
Verifies that all assets (JS, CSS, etc.) build correctly.
make build
To run the most critical local checks (test, webtest, lint, mypy) in one go:
make presubmit