Run any Skill in Manus with one click

changeset-validation

Stars3,371

Forks843

UpdatedMay 1, 2026 at 03:37

Validate changesets in openai-agents-js using LLM judgment against git diffs (including uncommitted local changes). Use when packages/ or .changeset/ are modified, or when verifying PR changeset compliance and bump level.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

openai

openai/openai-agents-js

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

7 files

SKILL.md

readonly

name	changeset-validation
description	Validate changesets in openai-agents-js using LLM judgment against git diffs (including uncommitted local changes). Use when packages/ or .changeset/ are modified, or when verifying PR changeset compliance and bump level.

Changeset Validation

Overview

This skill validates whether changesets correctly reflect package changes and follow the repository rules. It relies on the shared prompt in references/validation-prompt.md so local Codex reviews and GitHub Actions share the same logic. Experimental or preview-only feature additions that are explicitly labeled as such in the diff may remain a patch bump when they do not change existing behavior. Major bumps are only allowed after the first major release; before that, do not use major bumps for feature-level changes.

Quick start

Local (Codex-driven):

Run:
```
pnpm changeset:validate-prompt
```
Apply the rules from references/validation-prompt.md to the generated prompt.
Respond with a JSON verdict containing ok/errors/warnings/required_bump (English-only strings).

CI (Codex Action):

Run:

pnpm changeset:validate-prompt -- --ci --output .github/codex/prompts/changeset-validation.generated.md

Use openai/codex-action with the generated prompt and JSON schema to get a structured verdict.

Workflow

Generate the prompt context via pnpm changeset:validate-prompt.
Apply the rules in references/validation-prompt.md to judge correctness.
Provide a clear verdict and required bump (patch/minor/major/none).
If the changeset needs edits, update it and re-run the validation.

Branch-level changeset rule (do not skip)

If any .changeset/*.md file is already present in the current branch diff, treat it as the active changeset. Do not add a new changeset file.
Instead, update the existing changeset file by rewriting its summary to reflect the primary change relative to main. Do not try to capture every incremental update.
Keep the summary at one line; replace the line as needed rather than appending. If you must include multiple points, compress them into a single line.

Shared source of truth

Keep the prompt file as the single source of validation rules.
Keep the script lightweight: it should only gather context and emit the prompt.

Resources

references/validation-prompt.md

More from this repository

same repository

code-change-verification

openai/openai-agents-js

Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents JS monorepo.

2026-07-113.4k

runtime-behavior-probe

openai/openai-agents-js

Plan and execute runtime-behavior investigations with temporary TypeScript probe scripts, validation matrices, state controls, and findings-first reports. Use only when the user explicitly invokes this skill to verify actual runtime behavior beyond normal code-level checks, especially to uncover edge cases, undocumented behavior, or common failure modes in local or live integrations. A baseline smoke check is fine as an entry point, but do not stop at happy-path confirmation.

2026-07-043.4k

maintainer-review

openai/openai-agents-js

Review a GitHub issue or pull request URL as an openai-agents-js maintainer, with a staged assessment of whether the claim is real, practically important, already solvable with supported functionality, correctly scoped, better served by another design, and worth maintainer and contributor effort. Use when assessing issue validity or severity, deciding whether an issue should be prioritized or closed, determining whether a requested feature represents an unmet need rather than a discoverability or usage gap, judging whether a PR is worth bringing to mergeable quality, comparing open PRs or alternative designs, separating code quality from repository readiness, or drafting a concise maintainer assessment. When closure, additional evidence, or code changes should be requested, also produce a polite, concise, complete, copy-paste-ready maintainer comment.

2026-07-043.4k

examples-auto-run

openai/openai-agents-js

Run examples:start-all in auto mode with parallel execution, per-script logs, and start/stop helpers.

2026-06-233.4k

pr-draft-summary

openai/openai-agents-js

Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-agents-js. Must be used before the final response whenever the actual task diff includes runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size. Skip only when no eligible files changed, every change is repo-meta or docs-only without behavior impact, the task is conversation-only, or the user explicitly opts out.

2026-06-183.4k

implementation-strategy

openai/openai-agents-js

Decide how to implement runtime and API changes in openai-agents-js before editing code. Use when a task changes exported APIs, runtime behavior, schemas, tests, or docs and you need to choose the compatibility boundary, whether shims or migrations are warranted, and when unreleased interfaces can be rewritten directly.

2026-05-123.4k

name	changeset-validation
description	Validate changesets in openai-agents-js using LLM judgment against git diffs (including uncommitted local changes). Use when packages/ or .changeset/ are modified, or when verifying PR changeset compliance and bump level.

Changeset Validation

Overview

Quick start

Local (Codex-driven):

Run:
```
pnpm changeset:validate-prompt
```
Apply the rules from references/validation-prompt.md to the generated prompt.
Respond with a JSON verdict containing ok/errors/warnings/required_bump (English-only strings).

CI (Codex Action):

Run:

pnpm changeset:validate-prompt -- --ci --output .github/codex/prompts/changeset-validation.generated.md

Use openai/codex-action with the generated prompt and JSON schema to get a structured verdict.

Workflow

Generate the prompt context via pnpm changeset:validate-prompt.
Apply the rules in references/validation-prompt.md to judge correctness.
Provide a clear verdict and required bump (patch/minor/major/none).
If the changeset needs edits, update it and re-run the validation.

Branch-level changeset rule (do not skip)

If any .changeset/*.md file is already present in the current branch diff, treat it as the active changeset. Do not add a new changeset file.
Instead, update the existing changeset file by rewriting its summary to reflect the primary change relative to main. Do not try to capture every incremental update.
Keep the summary at one line; replace the line as needed rather than appending. If you must include multiple points, compress them into a single line.

Shared source of truth

Keep the prompt file as the single source of validation rules.
Keep the script lightweight: it should only gather context and emit the prompt.

Resources

references/validation-prompt.md