Menü
Release agent-harness packages to npm and verify publication. Use when the user asks to cut a release, push a missing release tag, or troubleshoot why a version was not published.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Create and manage MCP server config entities in the agent-harness workspace.
Create and manage MCP server config entities in the agent-harness workspace.
Create and manage lifecycle hook entities in the agent-harness workspace. Covers canonical event authoring, provider projection (Claude Code, GitHub Copilot, OpenAI Codex CLI, Cursor), mode behavior, handler types, the full event/provider support matrix, copy-paste recipes, and common diagnostics.
Create and manage lifecycle hook entities in the agent-harness workspace. Covers canonical event authoring, provider projection (Claude Code, GitHub Copilot, OpenAI Codex CLI, Cursor), mode behavior, handler types, the full event/provider support matrix, copy-paste recipes, and common diagnostics.
Run a multi-round critical review loop using specialized subagents. Use when the user asks to review changes, harden code, or ensure quality before merge. Spawns parallel review agents across security, core-logic, tests, CLI integration, and API surface, then iterates fix-and-re-review rounds until all agents report clean.
Create and manage skill entities in the agent-harness workspace. Use when the user wants to add a new skill, understand how skills work across providers, or generate provider skill artifacts from a canonical source.
| name | npm-workflow-release |
| description | Release agent-harness packages to npm and verify publication. Use when the user asks to cut a release, push a missing release tag, or troubleshoot why a version was not published. |
Run the release workflow for this repository end-to-end.
Use $ARGUMENTS as the target version when provided (for example: 1.6.0 or v1.6.0).
$ARGUMENTS is provided, normalize it to X.Y.Z and vX.Y.Z.packages/manifest-schema/package.json and packages/toolkit/package.json.version values are identical and equal to the target version..github/workflows/publish-npm.yml triggers on tag push (v*).GITHUB_REF_NAME=vX.Y.Z pnpm run release:guard before publishing.vX.Y.Z.git push origin vX.Y.Z.gh run list --workflow publish-npm.yml.gh run watch <run-id> --exit-status.npm view @madebywild/agent-harness-manifest dist-tags --jsonnpm view @madebywild/agent-harness-framework dist-tags --jsonlatest (or requested tag) points to X.Y.Z.NPM_TOKEN in GitHub Actions secrets.