What problem does it solve?
Teams running the shared om-auto-create-pr-loop workflow in the Open Mercato repository need repo-specific rules: which spec folders drive the work, which integration test suites gate completion, and which style checks apply before a pull request is considered done.
Core Features & Use Cases
- Spec source pinning: Directs the PR loop to specs under
.ai/specs/ and .ai/specs/enterprise/, with the run-folder contract defined in .ai/runs/README.md.
- Spec-completion gates: Defines
yarn test:integration (Playwright) plus yarn test:create-app:integration for template-synced surfaces as the required integration suites.
- Style compliance: Requires running the
om-ds-guardian skill whenever UI code was touched, and records Playwright transcripts as checkpoint artifacts.
- Use Case: An agent implementing a feature from an enterprise spec finishes coding, then follows this extension to run the Playwright integration suite, execute om-ds-guardian on changed UI, and attach the playwright.log transcript before opening the PR.
Quick Start
Ask the agent to run the auto-create-PR loop for a spec in .ai/specs/enterprise/ and apply the Open Mercato completion gates before opening the pull request.