development-workflow

To run scoped lint and tests on touched files, execute commands like pnpm lint <path> and pnpm test <path>. This ensures changes stay localized and safe by validating only the affected directories.

You can enforce mandatory follow-up steps like code generation or locale synchronization after API or locale changes. This workflow guardrail ensures dependent updates are never skipped during development.

Scoped workflow enforcement restricts lint and test execution to touched files or directories. It prevents unrelated failures and ensures localized changes remain safe across pull requests and local development tasks.

Yes, you can use pnpm for selective test execution by targeting specific paths. Running pnpm test <path> validates only the affected directories, satisfying requirements for localized and safe selective execution.

The best way to automate locale sync is by enforcing it as a mandatory follow-up step within your scoped workflow. This guardrail ensures locale synchronization automatically runs after relevant code changes.

Scoped linting works with both pull requests and local tasks. It enforces localized checks using pnpm lint <path> across your entire development workflow to keep changes safe regardless of environment.