skills.rest
go-musicfox
go-musicfoxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

om-setup-agent-pipeline

Configures the shared agent pipeline config, tracker descriptors, labels, and project docs for a repository.

2.6k|159|Updated Mar 8, 2021
Search Tags:#code review#sdlc#github cli#label taxonomy#agent pipeline#repository configuration#setup automation
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-setup-agent-pipeline-go-musicfox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-setup-agent-pipeline
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-setup-agent-pipeline
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-setup-agent-pipeline-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent skills in a repository need a consistent, committed configuration — validation commands, label taxonomy, tracker and browser providers — but setting that up by hand is error-prone and every skill breaks when it is missing. This skill performs the one-time setup so every other skill in the collection can read the same .ai/agentic.config.json. ## Core Features & Use Cases - Auto-detected configuration: Inspects the repo (package.json scripts, Makefile, Cargo.toml, go.mod, CI workflows) to detect validation commands and the default branch, then writes .ai/agentic.config.json after a short interview (or instantly with --defaults). - Tracker and browser descriptor installation: Copies the GitHub (gh CLI) tracker descriptor and a browser provider descriptor (agent-browser or Playwright) into .ai/trackers/ and .ai/browsers/, scaffolding custom providers from templates. - Label taxonomy and project docs: Creates the missing pipeline/category/priority/risk labels via the tracker and generates missing SDLC.md, AGENTS.md, CODE_REVIEW.md, and BACKWARD_COMPATIBILITY.md derived from the actual repository — never overwriting existing files. - Cross-skill coverage check: Verifies every skill referenced by installed skills is present and prints a paste-ready install command for anything missing. - Use Case: You just installed a collection of agent workflow skills into a repository. Run this skill once and it detects your pnpm test/build commands, installs the GitHub tracker descriptor, creates the review/merge-queue/needs-qa labels, generates an AGENTS.md routing table, and commits the config. ## Quick Start Run the om-setup-agent-pipeline skill in this repository to detect the toolchain and write the agent pipeline configuration.

Frequently Asked Questions about om-setup-agent-pipeline

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

FAQPage Schema
How do I set up the agent pipeline config in a new repository?▼

Run the om-setup-agent-pipeline skill once in the repository root. It detects your validation commands from package.json, Makefile, Cargo.toml, or go.mod, asks a few questions, and writes .ai/agentic.config.json plus the tracker descriptor. Use --defaults to skip all questions.

What does .ai/agentic.config.json contain?▼

It stores the base branch, tracker provider, browser provider, ordered validation commands, the label taxonomy (pipeline, category, meta, priority, risk), the QA gate toggle, CI wait limits, engine settings, and paths for runs, specs, scripts, and QA artifacts.

Does it overwrite my existing AGENTS.md or SDLC.md files?▼

No. Existing AGENTS.md, CLAUDE.md, SDLC.md, CODE_REVIEW.md, and BACKWARD_COMPATIBILITY.md files are never touched. The skill only generates documents that are missing, derives content from the actual repository, and shows each document before writing it.

Can I use a tracker other than GitHub, like Linear or Jira?▼

Yes. The skill scaffolds a new tracker descriptor from references/trackers/TEMPLATE.md at .ai/trackers/<name>.md, and you fill in the operations. Split setups are supported, for example issues in Linear with PR operations delegated to the GitHub descriptor.

What happens when the config already exists and I re-run setup?▼

The skill shows the current config and asks whether to update it, preserving every custom value you do not ask to change. Re-running is the intended path when the toolchain or label taxonomy changes.

Why does another skill say the pipeline is not configured?▼

Every skill in the collection loads .ai/agentic.config.json first and auto-runs this setup skill when it is missing. Once setup writes the config and installs the tracker descriptor, the calling skill re-runs its loading snippet and continues.

Related Skills

Explore More Software Engineering Skills→
tkoguttkogut
1

om-setup-agent-pipeline

Configures the shared agentic pipeline config, tracker descriptors, and project docs for a repository.

Community
Advanced
tkoguttkogut
1

om-auto-fix-pr

Drives an open pull request to merge-ready through review autofix, CI stabilization, and UI verification.

Community
Advanced
tkoguttkogut
1

om-apply-upgrade-notes

Synchronizes installed tracker and browser descriptors with shipped upgrade notes while preserving local edits.

Community
Advanced
AradotsoAradotso
4

tiez-clipboard-manager

Manage clipboard history with tags, privacy masking, and WebDAV or MQTT sync.

Official
Intermediate