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

om-followup-issue-from-pr

Creates follow-up GitHub issues from PRs with spec detection and labeling rules.

1.7k|382|Updated Sep 10, 2025
Search Tags:#gitHub#Open Mercato#Pull request#Labeling#Issue tracking#follow-up issue#spec detection
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill om-followup-issue-from-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-followup-issue-from-pr
Source: https://github.com/open-mercato/open-mercato/tree/main/.ai/skills/om-followup-issue-from-pr
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-followup-issue-from-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When reviewing pull requests in the Open Mercato repository, teams need a consistent way to convert review findings into tracked follow-up issues that correctly reference design specs and apply the right labels. This Skill extends the shared follow-up-issue workflow with repo-specific rules so nothing falls through the cracks.

Core Features & Use Cases

  • Spec Detection: Detects design specs in .ai/specs/ and .ai/specs/enterprise/, recognizing both {YYYY-MM-DD}-{kebab-case-title}.md filenames and legacy SPEC-* / SPEC-ENT-* naming, while ignoring already-implemented specs.
  • Enterprise Labeling: Automatically applies the enterprise category label when a follow-up references a spec under .ai/specs/enterprise/.
  • Tracking-Issue Template: Generates issues with a ## Spec section linking the spec path and stating the pickup path via /om-implement-spec or /om-auto-fix-issue.
  • Use Case: After merging a PR that partially implements a spec, use this Skill to file a follow-up issue that links the spec, applies correct labels, and tells the next developer exactly which command to run once the spec PR lands on develop.

Quick Start

Create a follow-up issue from this pull request using the om-followup-issue-from-pr workflow and link any related spec from .ai/specs/.

Frequently Asked Questions about om-followup-issue-from-pr

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

FAQPage Schema
How do I create a follow-up issue from a pull request?▼

Invoke the om-followup-issue-from-pr workflow after reviewing a PR. It detects any referenced design spec, applies the correct labels, and generates a tracking issue with a Spec section linking the spec path and the pickup command.

How are design specs detected in the Open Mercato repo?▼

Specs are detected in .ai/specs/ and .ai/specs/enterprise/ by filename. Files named {YYYY-MM-DD}-{kebab-case-title}.md count as specs, as do legacy SPEC-* and SPEC-ENT-* names. Files under .ai/specs/implemented/ are ignored.

When does the enterprise label get applied to a follow-up issue?▼

The enterprise category label is applied via the apply_label guard whenever the follow-up references a spec located in .ai/specs/enterprise/. This happens in addition to the shared labeling rules from the base skill.

What is the difference between om-implement-spec and om-auto-fix-issue?▼

Use /om-implement-spec when the follow-up requires implementing a design spec, and /om-auto-fix-issue for a scoped bug fix. The spec is actionable only after its spec PR is merged into develop.

Does this skill work outside the Open Mercato repository?▼

This is a repo-local extension of the shared om-followup-issue-from-pr skill installed from open-mercato/skills. It pins spec detection to .ai/specs/ paths, so it is intended for the Open Mercato repository layout.

Related Skills

Explore More Software Engineering Skills→
SafeAI-Lab-XSafeAI-Lab-X
1.0k

openclaw-pr-maintainer

Automate OpenClaw pull request triage, labeling, and evidence enforcement.

Community
Intermediate
SHGrowthSHGrowth
6

om-cto

Analyze platform gaps and orchestrate spec writing for Open Mercato.

Official
Advanced
zorgentechzorgentech

next-issues

List ARCHON project issues by status from GitHub Projects or repository.

Official
Intermediate
ahmedemad3ahmedemad3
60

speckit-taskstoissues

Convert tasks.md entries into GitHub issues via the GitHub MCP server.

Community
Intermediate