changeset

Estrellas2

Forks1

Actualizado17 de julio de 2026 a las 12:44

Decide whether a changeset is needed and draft it for open-managed-agents. Only @getoma/cli and @getoma/sdk are published; internal @duyet/oma-* packages never need one.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

duyet

duyet/oma

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

Más de este repositorio

mismo repositorio

create-agent

duyet/oma

Help users create and configure oma managed agents through conversation. Trigger when users say "create an agent", "I need an agent that...", "set up an agent for", "build me a bot", or describe a task to automate. Also trigger for "Create with AI" from Dashboard. Also use when users ask about the oma platform, what it can do, how to use the CLI, or how to configure resources.

2026-07-042

oma

duyet/oma

Use the oma platform to build, deploy, and manage AI agents. Trigger when users want to create agents, start sessions, manage environments, configure model cards, handle vaults/credentials, install skills, connect MCP servers, or interact with the oma HTTP API. Also trigger when users mention "oma", "openma", "managed agents", or ask how to deploy/run/manage an agent on oma.

2026-07-042

new-harness

duyet/oma

Scaffold a new agent harness for open-managed-agents and register it. Use when adding a new way to drive the model loop, like the default / acp-proxy / flue harnesses.

2026-07-032

preflight

duyet/oma

Run the full local pre-push gate (typecheck + all vitest pools) for open-managed-agents. Use before pushing or opening a PR — no CI workflow gates PRs in this repo, so this is the only gate.

2026-07-032

name	changeset
description	Decide whether a changeset is needed and draft it for open-managed-agents. Only @getoma/cli and @getoma/sdk are published; internal @duyet/oma-* packages never need one.

Determine whether the current change needs a changeset, then act.

See what changed: git diff --name-only origin/main...HEAD (or the staged / working diff).
A changeset is needed only if the diff touches packages/cli (@getoma/cli) or packages/sdk (@getoma/sdk) — the only published packages. Changes to apps, the console, docs, or any internal @duyet/oma-* package do not need one.
If needed, create .changeset/<short-slug>.md with frontmatter naming the affected published package(s). Both packages are pinned at 0.1.x until further notice — always use patch, never minor/major, regardless of change size. Follow the bump with a one-line, user-facing changelog summary:
```
---
"@getoma/cli": patch
---

Fix `oma sessions tail` reconnect after a dropped SSE stream.
```
Prefer pnpm changeset when an interactive terminal is available; otherwise write the file directly.
If not needed, say so briefly and do nothing.

Full release flow: the "Releasing @getoma/cli and @getoma/sdk" section of AGENTS.md.