Skip to content
TrustedSkillsbeta
Back to all skills

Changeset Validation

Official
openai·vlatest·other·MIT

Verifies proposed code changes against defined rules and best practices to ensure quality and consistency.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add openai/openai-agents-js --skill changeset-validation -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

openai

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: api.github.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.github.comsource host

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned openai/openai-agents-js at fdaf0a66ca.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
fdaf0a66ca
Manifest
.agents/skills/changeset-validation/SKILL.md
Scanned
8 files, 1,389 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

changeset-validation

What it does

This skill enables AI agents to automatically validate and format changesets before they are committed. It ensures that code modification summaries adhere to specific project standards, preventing invalid or malformed entries from reaching version control systems.

When to use it

  • Enforcing strict commit message conventions in monorepos where multiple packages are updated simultaneously.
  • Automating the review process for pull requests to catch formatting errors before human intervention.
  • Integrating into CI/CD pipelines to block deployments if changeset metadata is incomplete or incorrect.

Key capabilities

  • Automatic detection and correction of malformed changeset files.
  • Validation against predefined rules for scope, type, and description fields.
  • Prevention of invalid commits from being staged or pushed to repositories.

Example prompts

  • "Generate a valid changeset file for the breaking change I just made to the authentication module."
  • "Review my proposed changeset and fix any formatting errors before I commit."
  • "Validate the current state of my repository's changesets against the project's linting rules."

Tips & gotchas

Ensure your development environment has the necessary changeset CLI tools installed locally, as this skill often relies on external command execution to perform deep validation. Be aware that highly complex or non-standard commit histories may require manual overrides if automated parsing fails.