> ## Documentation Index > Fetch the complete documentation index at: https://docs.commonality.co/llms.txt > Use this file to discover all available pages before exploring further. # Introduction Commonality comes with a powerful monorepo linter that can be customized to scale standards for any existing tool or workflow. Checks can be run as part of your [CI pipeline](/continuous-integration/github-actions) to ensure a consistent developer experience across an infinite number of packages. Unlike a linter or static conformance tool, checks are dynamic functions that are run more like tests. This allows you to read and write to disk or even make network requests to validate your project's configuration. Checks can be [auto-fixable](/checks/creating-checks#auto-fixable-checks), have full type-safety, and are [easily testable](/checks/testing-checks) so you can ensure that you're creating the lowest friction possible for your team. Some examples of things you can do with checks: * Ensure that all packages have a `README.md` * Ensure that all `ui` packages have a `tsconfig.json` that supports JSX * Ensure that all NPM scripts have a corresponding Turborepo pipeline configured in `turbo.json` * Ensure that all `vite.config.js` files have matching build configuration for consistent inferred tasks with NX. Check out all our examples to quickly integrate into your existing workflows and tools. ## Running checks You can view the status of your checks by running the [check command](/reference/cli#check). ```bash theme={null} commonality check ```