Codex Open Meet Validate Changes with Package-Scoped Checks
Select lint, type checks, and tests according to the affected app or shared package. Expand verification when a contract affects multiple consumers.
中文Install in Codex
Codex with an Open Meet checkout, the current diff, package scripts, and a local test environment.
- Copy the entire pinned `.codex/skills/validate-changes/` directory to `.agents/skills/validate-changes/` in the target checkout.
- Open Codex in that checkout and invoke `$validate-changes` with the example task and desired output.
Example task
After editing a shared display-name type in a practice branch, invoke `$validate-changes`. Identify consumers and report the focused checks that ran for each affected app.What to check
The report names affected apps and packages, commands, results, and any checks that could not run.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should checks run for the whole repository?
Use the repo-wide matrix when multiple apps or shared behavior are affected. Start with the affected app for an isolated change.