go-musicfox
Official@go-musicfox
go-musicfox publishes the open-mercato om-* skill suite: an end-to-end pull request, issue triage, code review, and UX verification pipeline for repository maintainers.
Agent Skills by go-musicfox
Showing 37 vetted skills indexed across 1 GitHub repositories.
om-merge-buddy
Classify open pull requests by merge readiness from reviews, CI, labels, and mergeability.
om-setup-agent-pipeline
Configures the shared agent pipeline config, tracker descriptors, labels, and project docs for a repository.
om-spec-writing
Write and review feature specifications with skeleton-first drafting and severity-ranked architectural review.
om-auto-fix-issue
Automates end-to-end tracker issue resolution from triage through pull request review.
om-auto-create-pr
Executes autonomous coding tasks end-to-end and ships them as labeled pull requests.
om-ux-setup
Extracts a repository's design tokens, components, and screen archetypes into a committed .uxproof/ contract.
om-fix
Implements root-cause fixes with regression tests and validation gates in an autofix chain.
om-auto-implement-spec
Implements an existing spec into a reviewed, UI-verified pull request.
om-approve-merge-pr
Approves and squash-merges a pull request after enforcing label and QA gates.
om-auto-qa-pr
Verifies PR UI changes in a real browser and publishes screenshot evidence.
om-pipeline-retro
Classify finished pipeline runs and rank rework causes by wall-clock hours.
om-brainstorm
Guides divergent product conversations that converge on a routing decision and handoff brief.
om-auto-review-pr
Reviews pull requests in isolated worktrees and submits verdicts with labels and autofix loops.
om-ux-shape
Shape vague product and AI feature ideas into decided, implementation-ready directions.
om-root-cause
Diagnoses tracker-reported bugs and defines the minimal code change set for downstream fix agents.
om-close-fixed-issues
Close tracker issues that recently merged pull requests authoritatively fixed.
om-auto-continue-pr-loop
Resumes unfinished pull request runs from PLAN.md task tables in isolated git worktrees.
om-followup-issue-from-pr
Creates follow-up and tracking issues from PR comments and design documents.
om-check-and-commit
Runs configured validation gates, fixes failures, then commits and pushes the branch.
om-review-prs
Reviews all unreviewed open pull requests sequentially, newest first, via a delegated review workflow.
om-code-review
Reviews diffs, branches, and PRs against correctness, security, and breaking-change checklists with severity-ranked findings.
om-verify-in-repo
Triage tracker issues read-only to decide whether an autofix chain should proceed.
ask-anhoder
Routes user tasks to the appropriate om-* workflow skill and executes it.
om-auto-fix-pr
Drives an open pull request to merge-ready through review autofix, CI stabilization, and UI verification.
Frequently Asked Questions About go-musicfox
FAQPage SchemaWhat tasks can I accomplish with go-musicfox's om-* skills?▼
The suite covers the full PR lifecycle: filing and triaging tracker issues, writing staff-level specs, implementing fixes in isolated worktrees, running code review with severity-ranked findings, stabilizing CI, browser-based UI QA with screenshots, approving and squash-merging PRs, closing fixed issues, and drafting changelog release entries.
Who are the om-* skills designed for?▼
Repository maintainers and staff-level engineers managing active pull request and issue backlogs. The skills suit teams that enforce SDLC labels, validation gates, spec-first feature development, and evidence-based UX review, plus contributors who want autonomous issue-to-PR execution with claim locks preventing concurrent conflicts.
How do I set up and run the om-* skill pipeline?▼
Run om-setup-agent-pipeline once per repository. It inspects the default branch, validation scripts, and labels, writes .ai/agentic.config.json that every other skill reads, installs the tracker descriptor, and generates missing docs like SDLC.md and CODE_REVIEW.md. Re-run it whenever the toolchain or label taxonomy changes.
What prerequisites do the om-* skills require?▼
A configured tracker descriptor for issue and PR operations, a validation gate defined in the repo, and the generated .ai/agentic.config.json. UI verification skills (om-auto-qa-pr, om-ux-review-pr, om-integration-tests) additionally need a browser provider, provisioned via om-prepare-test-env, which writes a shared test-env descriptor.
Can the skills handle long or interrupted implementations?▼
Yes. om-auto-create-pr-loop handles multi-step spec implementations with a run folder (PLAN/HANDOFF/NOTIFY), one commit per step, and checkpoint verification with integration tests and screenshots. Interrupted runs resume via om-auto-continue-pr or om-auto-continue-pr-loop from the first unchecked plan step.