Updated 1d ago
by open-mercato
skills
Enterprise AI Engineering skills we coined at Open Mercato (1.2M+ lines of code ERP built with AI)
242 GitHub stars (242)
+34 in 20 days
| Period | New stars |
|---|---|
| Sep 27 | 0 |
| Sep 28 | 0 |
| Sep 29 | 0 |
| Sep 30 | +2 |
| Oct 1 | 0 |
| Oct 2 | +2 |
| Oct 3 | +4 |
| Oct 4 | 0 |
| Oct 5 | +1 |
| Oct 6 | +2 |
| Oct 7 | +2 |
| Oct 8 | +6 |
| Oct 9 | +4 |
| Oct 10 | 0 |
| Oct 11 | +2 |
| Oct 12 | +2 |
| Oct 13 | +1 |
| Oct 14 | +5 |
| Oct 15 | 0 |
| Oct 16 | +1 |
- 30 skills (30 skills found in its SKILL.md files)
- 35 forks (35 forks)
- 1d ago last update (Last updated 1d ago)
Install
Skills CLI
npx skills add open-mercato/skills
Asks which skills and agents to install. Just one: npx skills add open-mercato/skills --skill om-apply-upgrade-notes — add -g for every project.
Claude Code
git clone https://github.com/open-mercato/skillscp -r "skills/skills/om-apply-upgrade-notes" ~/.claude/skills/
Copies the om-apply-upgrade-notes skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add open-mercato/skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 42 files.
-
om-apply-upgrade-notes
Apply the skills collection's UPGRADE_NOTES.md after an upgrade. Re-syncs installed tracker and browser-provider descriptors while preserving local edits, reports custom-provider gaps, checks pipeline config and installed artifacts, and summarizes exactly what changed.
skills/om-apply-upgrade-notes/SKILL.md on GitHub (opens in a new tab) -
om-approve-merge-pr
Approve (submit an approving review) and squash-merge a PR given only its number, refusing when the QA gate or a blocking label forbids it. Routes fixable blockers to om-auto-fix-pr (red CI via its --ci-only mode, or conflicts and review problems via the full loop). Optionally file a follow-up issue at the same time. Use when the user says "approve and merge PR 123", "ship PR 123", or gives a PR…
skills/om-approve-merge-pr/SKILL.md on GitHub (opens in a new tab) -
om-auto-continue-pr-loop
Advanced om-auto-continue-pr for PRs started by om-auto-create-pr-loop — claims the PR, resumes from the first non-done PLAN.md Tasks row in an isolated worktree, keeps the per-step commit and checkpoint discipline (integration tests + screenshots for UI), runs the full gate at completion, keeps spec-only design PRs design-only (implementation ships on its own PR via om-auto-implement-spec), and…
skills/om-auto-continue-pr-loop/SKILL.md on GitHub (opens in a new tab) -
om-auto-continue-pr
Resume any open PR — started by `om-auto-create-pr` or opened outside the pipeline. Claims it, resumes in an isolated worktree from the first unchecked step of its execution plan; a PR with no plan is adopted — the goal is reconstructed from its description, comments, review feedback, linked issues and diff, then executed. Usage - /om-auto-continue-pr <PR-number>
skills/om-auto-continue-pr/SKILL.md on GitHub (opens in a new tab) -
om-auto-create-pr-loop
Advanced om-auto-create-pr for long, multi-step spec implementations needing resumability and strict step tracking — run folder (PLAN/HANDOFF/NOTIFY), one lean commit per Step, checkpoint verification every ~5 Steps with integration tests and UI screenshots, full gate at completion, ready labeled PR. Resumable via om-auto-continue-pr-loop. Use plain om-auto-create-pr for small fixes.
skills/om-auto-create-pr-loop/SKILL.md on GitHub (opens in a new tab) -
om-auto-create-pr
Run an arbitrary autonomous task end-to-end and ship it as a PR against the configured base branch. Drafts a Progress-tracked execution plan, commits on a fresh worktree branch, implements phase-by-phase, runs the configured validation gate, applies pipeline labels. Long plans hand off to om-auto-create-pr-loop automatically. Resumable via om-auto-continue-pr.
skills/om-auto-create-pr/SKILL.md on GitHub (opens in a new tab) -
om-auto-fix-issue
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain (om-verify-in-repo, om-root-cause, om-fix, om-open-pr, om-auto-review-pr, om-auto-qa-pr for UI fixes) or the feature route (spec via om-auto-write-spec, built via om-auto-implement-spec). Isolated wor…
skills/om-auto-fix-issue/SKILL.md on GitHub (opens in a new tab) -
om-auto-fix-pr
Drive an open PR to merge-ready from its number — merges the latest base, then loops review-autofix (om-auto-review-pr), built-in CI stabilization, and UI verification (om-auto-qa-pr) until approvable, green, and QA-evidenced. A --ci-only mode drives just CI green on a PR or a plain branch. Files follow-up issues for nits, normalizes labels, hands off to om-approve-merge-pr — never merges itself.…
skills/om-auto-fix-pr/SKILL.md on GitHub (opens in a new tab) -
om-auto-implement-spec
Implement an existing spec and ship a verified, reviewed, ready PR. Resolves the spec by path, name, issue, or spec-PR number (clean stop with candidates when not found). A spec PR stays design-only — implementation ships on its own PR referencing it. Delegates to om-auto-create-pr (om-auto-continue-pr for an existing implementation PR), then runs the review loop and UI verification with screensh…
skills/om-auto-implement-spec/SKILL.md on GitHub (opens in a new tab) -
om-auto-manage-issues
Bring existing tracker issues up to standard without implementing anything — applies missing SDLC labels, clarifies laconic issues (analyzing attached screenshots), posts a read-only implementation-prep analysis, checks each issue against SDLC.md's Definition of Ready (READY_STATUS, not-ready comment), and flags feature issues lacking a covering spec (optionally authoring one with --write-missing…
skills/om-auto-manage-issues/SKILL.md on GitHub (opens in a new tab) -
om-auto-qa-pr
QA a PR's UI change in a real browser through the configured browser-provider descriptor — first ensuring the PR has been reviewed (invoking om-auto-review-pr when it has not), then capturing screenshots and a pass/fail report, and optionally posting tracker evidence or self-QA labels without modifying source. Also runs in a local, tracker-less mode against the current worktree.
skills/om-auto-qa-pr/SKILL.md on GitHub (opens in a new tab) -
om-auto-review-pr
Review or re-review a PR by number in an isolated worktree. Runs the `om-code-review` skill — or, for spec-only design PRs, a specification review — submits approve/request-changes, manages pipeline labels. On changes-requested, the autofix loop (fix/test/validate/re-review until merge-ready) runs on the automation's own PRs or with --autofix; other authors' PRs get review + handoff only. Usage -…
skills/om-auto-review-pr/SKILL.md on GitHub (opens in a new tab) -
om-auto-update-changelog
Draft a CHANGELOG.md release entry in an emoji-driven format for every PR merged since the last release, then delegate to om-auto-create-pr so it lands as a docs PR against the configured base branch. Honors the Supersede Credit Rule and verifies every credit against commit authorship, so carry-forwards and umbrella merges credit the contributor rather than the merger. Use at release time.
skills/om-auto-update-changelog/SKILL.md on GitHub (opens in a new tab) -
om-auto-write-spec
Autonomously turn a brief or FR issue into a spec landed on a ready PR — runs om-spec-writing --autonomous (defaults posted for override), attaches UI mockups and current-app screenshots as PR evidence when a browser provider exists, applies full SDLC labels, and emits PR/spec markers for chaining into om-auto-implement-spec. Use for "write a spec for X and open a PR", "spec this issue".
skills/om-auto-write-spec/SKILL.md on GitHub (opens in a new tab) -
om-backlog
Turns a product brief (its Scope and Key flows) or a spec's Phasing into a tracker backlog — epics, stories with acceptance criteria, tasks — with stable ids in titles, epic checklists, and Epic links, filing every issue through om-prepare-issue so dedupe, SDLC labels, and rationale come for free. Refuses a brief that is not ready; shows the whole tree and waits before writing. Use for "build the…
skills/om-backlog/SKILL.md on GitHub (opens in a new tab) -
om-brainstorm
Divergent conversation before any artifact exists — open questions one at a time, alternatives including building nothing, converging on a routing decision and a handoff brief for the next skill. Runs before om-spec-writing and om-prepare-issue. Use when the user says "should we build this", "let's think this through", "I have an idea", "is this worth doing".
skills/om-brainstorm/SKILL.md on GitHub (opens in a new tab) -
om-check-and-commit
Verify that the current branch is ready to publish by running every configured validation command in order, fix straightforward failures (including locale-file drift when the repo checks it), and once everything passes commit and push the current branch. Use when the user asks to check the branch, make CI-style verification pass, then commit and push.
skills/om-check-and-commit/SKILL.md on GitHub (opens in a new tab) -
om-close-fixed-issues
Close the tracker issues that recently merged PRs authoritatively fixed — via `fixes`/`closes`/`resolves` keywords or `closingIssuesReferences` — and post informational comments on issues whose PRs were closed without merging or merged into a non-base branch. Use for post-merge housekeeping and release prep. Respects claim locks and never acts on bare `#N` mentions.
skills/om-close-fixed-issues/SKILL.md on GitHub (opens in a new tab) -
om-code-review
Review a diff, branch, or PR against correctness, security, breaking-change, and quality standards — runs the validation gate, applies the built-in checklist plus any repo-local one, and produces severity-ranked findings with an approve/request-changes verdict. The review engine behind om-auto-review-pr and om-review-prs.
skills/om-code-review/SKILL.md on GitHub (opens in a new tab) -
om-create-skill
Author a new OM skill from a brief, or split an oversized SKILL.md into layered references/ files — conservatively, behind the lint + completeness gate. Knows the layering philosophy, lint invariants, tracker abstraction, and the cross-skill contract, so output matches house conventions. Use for "create a skill for…", "new om-skill", "split this skill into references".
skills/om-create-skill/SKILL.md on GitHub (opens in a new tab) -
om-discover
Guide a product discovery conversation and write product-brief.md with the problem, evidence, scope, decisions, and the next uncertainty to resolve. Use for product discovery, defining a product, or refreshing its brief. Supports existing products, client ideas, and own ideas.
skills/om-discover/SKILL.md on GitHub (opens in a new tab) -
om-fix
Implements the minimal code change identified by the om-root-cause step, adds regression tests, and runs the configured validation gate. Claims the tracker issue at start (assignee + in-progress label + claim comment) so concurrent automation backs off. Does not commit, push, or open a PR — that is the om-open-pr step's job.
skills/om-fix/SKILL.md on GitHub (opens in a new tab) -
om-followup-issue-from-pr
Turn a PR into tracked follow-up work — paste a PR or PR-comment link to extract the actionable ask and open a follow-up issue assigned to the @-mention or PR author; for a PR adding a design doc, it opens the missing `Implement:` tracking issue instead. Use for "make a follow-up issue", "create an issue for this", or a pasted PR/comment link with that intent.
skills/om-followup-issue-from-pr/SKILL.md on GitHub (opens in a new tab) -
om-integration-tests
Run and create integration/E2E tests by exploring the live app with the configured browser provider, preserving repository-native runners, reusing the shared test environment, and diagnosing failures from concrete artifacts.
skills/om-integration-tests/SKILL.md on GitHub (opens in a new tab) -
om-merge-buddy
Scan open pull requests via the configured tracker, classify merge readiness from labels, reviews, CI, and mergeability, then report which PRs can merge now and which ones are close but blocked.
skills/om-merge-buddy/SKILL.md on GitHub (opens in a new tab) -
om-mockup-prototype
Build a neutral clickable low-fi prototype from a product brief during discovery, after the first synthetic panel and before refreshing the brief or drafting a backlog. Preserve business rules and explicit assumptions, simulate the chosen flow locally, and verify navigation and relevant states in a browser. Use for discovery wireframes or testing a flow before detailed design.
skills/om-mockup-prototype/SKILL.md on GitHub (opens in a new tab) -
om-open-pr
Shared PR opener for the auto pipeline — commits the worktree, pushes, reuses an existing PR or opens a ready (non-draft) PR against the configured base branch with the unified body template, applies the full SDLC label set with rationale comments, and for issue-driven runs hands the issue back and releases the lock. Emits the `PR:`/`Issue:` chaining reference lines.
skills/om-open-pr/SKILL.md on GitHub (opens in a new tab) -
om-pipeline-retro
Classify finished pipeline runs from the configured tracker — clean single pass, hard recovery, loop checkpoints, or cause not recorded — and rank what the second passes cost in wall-clock hours. Read-only; hands the top cause to om-prepare-issue. Use for "pipeline retro", "why is our pipeline slow", "what is costing us rework".
skills/om-pipeline-retro/SKILL.md on GitHub (opens in a new tab) -
om-pr-autopilot
Diagnose what state one open PR is actually in — unfinished plan steps, missing review, unresolved conversations, red CI, base conflicts, missing QA evidence, merge-ready — then run the matching chain of om-* skills in order and publish a status report. Use for "finish PR 123", "what is left on PR 123", "drive PR 123 to the end".
skills/om-pr-autopilot/SKILL.md on GitHub (opens in a new tab) -
om-prepare-issue
Create one well-formed tracker issue from a brief without implementing it — dedupes against existing issues and PRs, links a covering spec (authoring one via om-auto-write-spec on a design-only PR when a feature needs it), attaches user-provided images as tracker evidence, otherwise embeds step-by-step guidance, and applies SDLC labels on creation. For existing issues use om-auto-manage-issues. U…
skills/om-prepare-issue/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.