What problem does it solve? Writing Mergify configuration files (.mergify.yml) is error-prone because the schema, conditions syntax, and available actions evolve over time, and mistakes are only discovered after pushing changes to the repository. This Skill validates configuration locally against the official JSON schema and simulates what Mergify would do on a real pull request before committing. ## Core Features & Use Cases - Config Validation: Run mergify config validate to check .mergify.yml, .mergify/config.yml, or .github/mergify.yml against the official schema, with per-error path and message output and CI-friendly exit codes. - PR Simulation: Run mergify config simulate <PR_URL> to preview the actions Mergify would take on a specific pull request using the local configuration file. - Documentation-Grounded Authoring: Fetches the relevant pages from docs.mergify.com (file format, conditions, actions, merge queue rules) before writing or editing configuration, avoiding outdated memorized knowledge. - Use Case: Before pushing a new merge queue rule, validate the edited config locally, simulate it against an open PR to confirm the rule triggers as expected, then commit with confidence. ## Quick Start Ask the assistant to validate your Mergify configuration file and simulate it against a specific pull request URL to preview the resulting actions.
