skills.rest
open-mercato
open-mercatoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

om-auto-continue-pr-loop

Extends the shared auto-continue PR loop with Open Mercato spec gates and legacy plan resume support.

1.7k|382|Updated Sep 10, 2025
Search Tags:#Automation#Integration Testing#Workflow#SPEC-driven#ci gates#Open Mercato#Pull request
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-continue-pr-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-auto-continue-pr-loop
Source: https://github.com/open-mercato/open-mercato/tree/main/.ai/skills/om-auto-continue-pr-loop
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-continue-pr-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams running autonomous PR continuation loops in the Open Mercato repository need repo-specific rules: which specs count as done, which integration suites must pass, and how to resume PRs created before the run-folder migration. This extension pins those details so the shared workflow behaves correctly in this repo.

Core Features & Use Cases

  • Spec-completion gates: Defines that completion requires yarn test:integration plus yarn test:create-app:integration when template-synced surfaces changed, and the om-ds-guardian style pass when UI was touched.
  • Spec scope pinning: Restricts spec sources to .ai/specs/ and .ai/specs/enterprise/, with the run-folder contract defined in .ai/runs/README.md.
  • Legacy plan resume: Detects flat Tracking plan: .ai/runs/<date>-<slug>.md references in older PRs, migrates them into a run folder with PLAN.md, and initializes HANDOFF.md and NOTIFY.md.
  • Use Case: An agent resuming a stale PR finds a legacy flat plan, migrates it into the run-folder structure, then runs the correct Docker-or-local validation gates before marking the spec complete.

Quick Start

Ask the agent to continue the open PR loop for this repository using the Open Mercato spec-completion gates and run-folder conventions.

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

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

FAQPage Schema
How do I resume an old PR with a legacy flat tracking plan?▼

Create a run folder at .ai/runs/<date>-<slug>/, move the flat plan file in as PLAN.md, and initialize HANDOFF.md and NOTIFY.md as part of the resume's first commit. The skill then follows the standard run-folder contract.

What tests must pass before a spec is considered complete in Open Mercato?▼

Completion requires yarn test:integration, plus yarn test:create-app:integration when template-synced surfaces changed. If UI was touched, the om-ds-guardian style-compliance pass is also required.

Where are specs located for the auto-continue PR loop in this repo?▼

Specs live in .ai/specs/ or .ai/specs/enterprise/ for enterprise scope. The run-folder contract governing execution state is documented in .ai/runs/README.md.

Should validation run in Docker or locally?▼

Choose Docker versus local execution according to the Validation Commands section of the root AGENTS.md file before running any spec-completion gate.

Does this skill work standalone without the shared om-auto-continue-pr-loop skill?▼

No. It is a repo-local extension that relies on the shared skill installed at .agents/skills/om-auto-continue-pr-loop/SKILL.md from the open-mercato/skills repository, and only adds repo-specific overrides.

Related Skills

Explore More Software Engineering Skills→
SHGrowthSHGrowth
6

om-cto

Analyze platform gaps and orchestrate spec writing for Open Mercato.

Official
Advanced
openaiopenai
5.3k

finishing-a-development-branch

Guides merging, pushing, or keeping a completed development branch with worktree cleanup.

Official
Advanced
Pyl-TechPyl-Tech

verification-loop

Runs prioritized verification checks for builds, types, lint, tests, security, spec conformance, and silent-failures before merging PRs.

Official
Advanced
mitchellfyimitchellfyi
3

dex

Automate ticket-to-pull-request workflows with planning, code review, verification, and PR follow-through.

Community
Advanced