REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
This repo is a collection of 42 skills
Enterprise AI Engineering skills we coined at Open Mercato (1.2M+ lines of code ERP built with AI)Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/skills/open-mercato-skills)MCP-Server, die die KI für dieselbe Arbeit mit Diensten verbinden
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
Gleiche Art Arbeit, sortiert wie die Skill-Liste
| Dieser skills | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Anbieter | open-mercato | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 42 | 1 | 1 | 1 | 1 |
| GitHub-Sterne | 279 | 467.235 | 234.125 | 149.873 | 144.332 |
| Letzte Codeänderung | 13. Nov. 2026 | 18. Nov. 2026 | 20. Apr. 2026 | 18. Nov. 2026 | 18. Nov. 2026 |
| Lizenz | MIT | MIT | – | Apache-2.0 | MIT |
42 Skills (Anweisungssammlungen) von open-mercato, die eine KI liest und befolgt · kein MCP-Server
Install only the ones you use. Open a skill to see how to install it
This set has 42 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below
Showing 30 of 42 See all on GitHub
Use when upgrading the skills collection, e.g. 'apply the upgrade notes'. Sync installed tracker and browser descriptors while preserving local edits, check pipeline config and installed artifacts, and report custom-provider gaps and changes.
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 issu…
Use when an open PR needs unfinished work resumed, e.g. 'continue PR 123'. Claim it and continue its execution plan in an isolated worktree, or reconstruct a plan from the PR context when none exists. Validate and update the same PR; long plans hand off to om-auto-continue-pr-loop.
Use when resuming a long om-auto-create-pr-loop run, e.g. 'resume PR 123 from its next step'. Claim the PR, resume its PLAN.md Tasks in an isolated worktree, preserve per-step commits and checkpoint tests with UI screenshots, then run the full gate. Keep spec-only PRs design-only; use om-auto-conti…
Use when a task should be implemented autonomously and delivered as a PR, e.g. 'build this and open a PR'. Write a tracked execution plan, implement in an isolated worktree, run configured validation, and apply pipeline labels. Long plans hand off to om-auto-create-pr-loop; resume via om-auto-conti…
Use for long, multi-step tasks needing strict tracking and resumability, e.g. 'implement this spec step by step'. Create a run folder, commit each Step, verify checkpoints with integration tests and UI screenshots, then run the full gate and open a ready labeled PR. Resume via om-auto-continue-pr-l…
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…
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 f…
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-continu…
Use when existing issues need triage or clearer requirements, e.g. 'clean up these issues'. Apply SDLC labels, clarify issues and screenshots, post prep analysis, check Definition of Ready, and flag missing feature specs; optionally write them with --write-missing-specs. Handle one issue or a batch…
Use when a PR's UI needs browser QA, e.g. 'test PR 123 in the browser'. Ensure review first, capture screenshots and a pass/fail report through the configured browser provider, and optionally post evidence or self-QA labels without changing source. Also supports local QA without a tracker.
Use when a PR needs review or re-review, e.g. 'review PR 123'. Review code or a spec-only design in an isolated worktree, submit approve/request-changes, and manage pipeline labels. Fix/test/re-review automatically for the automation's own PRs or with --autofix; hand other authors the findings.
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-for…
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…
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.…
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…
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,…
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 rel…
Use when a diff, branch, or PR needs a correctness and security review, e.g. 'review this diff'. Run validation and the built-in plus repository checklist, check breaking changes and quality, and return severity-ranked findings with an approve/request-changes verdict. Powers om-auto-review-pr and o…
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 "c…
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.
Use when a confirmed issue has an om-root-cause brief ready to implement, e.g. 'apply this issue fix'. Used by om-auto-fix-issue. Claim the issue, make the minimal change, add regression tests, and run configured validation. Leave commit, push, and PR creation to om-open-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…
Use when live-app integration or E2E tests need running, creating, or debugging, e.g. 'add browser coverage for this flow'. Explore with the configured browser provider, preserve repository-native runners, reuse the shared test environment, and diagnose failures from concrete artifacts.
Use when you need a read-only view of which PRs can merge, e.g. 'what is ready to merge?'. Scan open PRs through the configured tracker, assess labels, reviews, CI, and mergeability, then report ready PRs and those close but blocked.
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…
Use when validated changes must ship as a PR, e.g. 'open a PR for this'. Commit and push, reuse an existing PR or open a ready PR against the configured base branch, apply SDLC labels and rationale, and hand back issue-driven claims. Emit PR and Issue chaining references.
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…
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…
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-…
MCP = die Hände
Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.
Skill = das Handbuch
Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.
Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.
Claude CodeCodexCursorOpenCode
Laut README des Anbieters und den Ordnern im Repo
This repo has 42 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.