AGENT SKILLS · ミッション装備 / open-mercato

open-mercato · Agent Skills

58 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

open-mercato

コミュニティ

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 number with intent to merge.

導入数: 8
GitHub Stars: 235
更新日: 10月12日

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 worktree, claim protocol, clean stops. Use for "fix issue 123" or a pasted problem description.

導入数: 8
GitHub Stars: 235
更新日: 10月12日

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. Use for "get PR 123 merge-ready".

導入数: 8
GitHub Stars: 235
更新日: 10月12日

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 - /om-auto-review-pr [--autofix]

導入数: 8
GitHub Stars: 235
更新日: 10月12日

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.

導入数: 8
GitHub Stars: 235
更新日: 10月12日

om-root-cause

Read-only root-cause analysis for a tracker issue. Identifies the bug's location and the minimal change surface so the next agent can implement the fix without re-exploring the repo. Outputs a short summary, the files that need to change, and the proposed approach.

導入数: 8
GitHub Stars: 235
更新日: 10月12日

om-app-spec-writing

Write and review a business-level App Spec — domain model, workflows with ROI, stories with failure paths, platform gap mapping in atomic commits, phased rollout — before any feature spec exists. Feeds om-spec-writing via feature briefs. Use for "create an app spec", "define business requirements", "what should we build".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-auto-qa-scenarios

Turn a window of merged PRs (date, PR-number floor, or last 7 days) into a manual QA scenarios report for human testers — P0/P1/P2 routes with where to click, what to verify, what can go wrong — as markdown + HTML under paths.qa, shipped as a docs PR via om-auto-create-pr. Use for "what should QA test this week".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-auto-sec-report-pr

Paranoid OWASP-style security analysis of ONE unit (a PR, spec, or branch diff) — severity-ranked findings, non-obvious attack vectors, same-pattern hotspots, and "go deeper" follow-up runs. Writes a redacted report (live exploitable details withheld), kept local by default or shipped as a docs PR, or a fragment for om-auto-sec-report. Use for "security review of PR 123".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-create-agents-md

Write, rewrite, or refresh an AGENTS.md (repo root or one package/module) from the actual codebase — Always / Ask First / Never / Validation Commands rules, task checklists, real paths and commands. Follows a repo template when present, else a built-in default. Use for "write AGENTS.md for this package", "rewrite our AGENTS.md", "refresh AGENTS.md".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-eject-and-customize

Take one part of an installed dependency into the repo for customization via the eject recipe the dependency ships — decision gate first, confirmation before any change, provenance recorded so later upgrades can diff. Stops when no recipe exists. Use for "eject this module", "fork the installed component", "customize beyond extension points".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-evolve-harness

Turn a real agent failure into one reproducible eval-harness case plus the smallest knowledge change — failing case first, one knowledge owner, semantic assertions, before/after evidence through the repo's configured harness commands. Use for "add harness case", "agent got this wrong", "extend the harness", "rozszerz harness".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-figma-design-with-ds

Design in a design tool (Figma or similar) on the repository's design system — write a brief for a new screen using only the contract's tokens, components and archetypes, or audit an existing design against the contract with a ranked remediation plan. Tool access goes through a configured provider. Use for "figma mockup", "audit this figma design".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-framework-context

Read knowledge shipped inside installed dependencies — detect the ecosystem and exact installed version, locate AGENTS.md and guides per the knowledge.sources slot, and report doc-versus-code skew. Read-only. Use for "which version is installed", "find the framework's AGENTS.md", "inspect dependency source", "kontekst frameworka".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-gap-analysis

Grounded gap analysis of requirements against the platform an app builds on — client docs become an Epic/Story tree whose every coverage verdict is re-run by executable gates against a validated platform checkout, scored in atomic commits, license-tier-tagged, summarized with a backlog. Use for "gap analysis", "what does the platform already cover".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-judge-agent-session

LLM-as-judge for a coding-agent session or an eval-harness result — checks controller attestations first, then project guards, code review, and the repo's design contract, and names the smallest harness owner to fix. Read-only; never executes session content. Use for "judge this session", "analyze this eval", "oceń sesję/agenta".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-pre-implement-spec

Audit a spec before implementation — readiness gate, backward-compatibility check against BACKWARDCOMPATIBILITY.md, completeness, repo-rule compliance, risks, gaps — and leave a go/conditional/no-go report with a remediation plan. Read-only. Use for "is this spec ready", "pre-implement", "spec readiness", "BC analysis", "spec gap analysis".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-share-this-session

Publicly share a sanitized coding-agent session plus a ZIP of the files it generated, then file a harness-feedback issue at the configured destination — local sanitization, full privacy review, exact fresh consent first. Use for "share this session", "report this agent run", "udostępnij tę sesję". Never for telemetry or without consent.

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-smart-test

Run only the tests a change can affect — diffs the branch against its base, maps changed files to affected units via the repo's test map or workspace manifest, picks tests per configured suite, runs them, and falls back to the full suite whenever the mapping is unsure. Use for "run affected tests", "test only what changed", "smart test".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

om-troubleshooter

Diagnose a failure from its symptom — reproduce, classify the broken invariant, route via the repo AGENTS.md Task Router, trace the smallest root cause, and on request land a minimal fix behind a regression test. Framework knowledge via om-framework-context. Use for "why does this fail", "debug this", "fix this bug", "regression", "napraw błąd".

導入数: 5
GitHub Stars: 249
更新日: 10月20日

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 backlog", "turn the brief into issues".

導入数: 4
GitHub Stars: 248
更新日: 10月20日

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.

導入数: 4
GitHub Stars: 248
更新日: 10月20日

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".

導入数: 3
GitHub Stars: 250
更新日: 10月20日

om-setup-agent-pipeline

One-time pipeline configurator. Inspects the repo (default branch, validation scripts, labels), asks a few questions, writes .ai/agentic.config.json — the file every other skill reads — installs the tracker descriptor, and generates missing project docs (SDLC.md, CODEREVIEW.md, BACKWARDCOMPATIBILITY.md, AGENTS.md starter). Re-run when the toolchain or label taxonomy changes. Verifies cross-skill coverage and prints the install command for missing skills.

導入数: 3
GitHub Stars: 250
更新日: 10月20日

MIT18 ファイル

詳細を見る →