om-auto-create-pr-loop

Extends the shared auto-create-PR workflow with Open Mercato spec gates and integration test requirements.

1.7k|382|Updated Sep 10, 2025
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-create-pr-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-auto-create-pr-loop
Source: https://github.com/open-mercato/open-mercato/tree/main/.ai/skills/om-auto-create-pr-loop
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-create-pr-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about om-auto-create-pr-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the auto-create-PR loop in the Open Mercato repo?

Follow the shared om-auto-create-pr-loop skill installed at .agents/skills/, then apply this repo extension: drive work from a spec in .ai/specs/ or .ai/specs/enterprise/ and satisfy the Open Mercato completion gates before opening the PR.

What integration tests gate spec completion in Open Mercato?

The gate is yarn test:integration, which runs the Playwright integration suite. When the change touches template-synced surfaces, yarn test:create-app:integration must also pass before the spec is considered complete.

When is the om-ds-guardian skill required in the PR loop?

The om-ds-guardian style-compliance pass is required whenever the change touched UI code. It runs as part of the spec-completion gates alongside the integration test suites.

Should I run validation with Docker or locally in Open Mercato?

Choose Docker versus local execution according to the Validation Commands section of the root AGENTS.md file. Pick that mode before running any of the completion gate commands.

What checkpoint artifacts does the PR loop produce?

Browser-automation checkpoints are recorded as Playwright transcripts in a playwright.log file, matching the Open Mercato QA setup. These transcripts document the automated browser verification steps.