New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Changeset

by romeerez in romeerez/orchid-orm

“Use when the user prompts "changeset".”

— description from SKILL.md by romeerez
MITAuto-check passedDatabases

Install Changeset

skills CLI
$ npx skills add romeerez/orchid-orm --skill changeset -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install romeerez/orchid-orm changeset --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/romeerez/orchid-orm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/changeset .claude/skills/changeset && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
changeset
GitHub stars
543
Token cost
~945 tokens
SKILL.md length
450 words
Files
2
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

  • Works in 9 steps: Determine the change scope. → Determine the issue number. → Classify the release type. → …
  • SKILL.md covers Overview, Workflow, Quick Reference and Examples, plus 1 more section
  • Calls pnpm, git and changeset

About this skill

Changeset is a skill in romeerez/orchid-orm (543 stars). Its SKILL.md is about 945 tokens, with 1 other file in the folder. Licence: MIT.

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Determine the change scope.
  2. Determine the issue number.
  3. Classify the release type.
  4. Determine affected packages.
  5. For a minor change, prepend a section to BREAKING_CHANGES.md.
  6. From the repo root, run
  7. Edit the generated .changeset/*.md file printed by the command.
  8. Before committing, print the generated outputs and ask for confirmation.
  9. Stage and commit

What it can do on your machine

Read from SKILL.md and the folder at commit de54a3b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • git
    • changeset

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Changeset loads about 945 tokens when it runs. Until then it costs about 12 tokens; SKILL.md has 450 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~12
When it runs · the whole SKILL.md, loaded when a task matches
~945

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from romeerez/orchid-orm at commit de54a3b, republished under its MIT licence (© romeerez). 450 words, ~945 tokens.

Download SKILL.mdSave it as .claude/skills/changeset/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
changeset
description
Use when the user prompts "changeset".

Changeset

Overview

Create the release changeset, optional breaking-change note, staging, and commit. Order matters: scope, patch/minor classification, file edits, exact-message commit.

When this skill is active, follow only this skill for the changeset task. Ignore other process skills, including superpowers skills, unless the user explicitly asks for them.

Workflow

  1. Determine the change scope.
    • If the prompt describes the change directly, use that description.
    • If the prompt is like 611 1, find changes/611*/1*/spec.md and read it.
    • If the scope is still unclear, ask the user before continuing.
  2. Determine the issue number.
    • Prefer the numeric prefix from a changes/ directory.
    • Otherwise use the prompt's issue number.
    • If no issue number is known, ask the user; the changeset and commit message must end with (#<issue-number>).
  3. Classify the release type.
    • patch: adding new functionality.
    • patch: extending existing functionality while preserving previous contracts.
    • minor: any backward-compatibility gap or breaking behavior/API change.
  4. Determine affected packages.
    • Include packages whose public behavior/API changed.
    • Use each package's name from packages/<folder>/package.json in the changeset file.
    • If pqb or rake-db are affected, always include orchid-orm.
    • If pqb or rake-db is minor, orchid-orm is also minor.
  5. For a minor change, prepend a section to BREAKING_CHANGES.md.
    • Describe before, after, and upgrade steps.
    • Grep current affected versions from packages/*/package.json.
    • Title: affected packages and versions after this release by incrementing minor and setting patch to 0.
    • Keep the section short and clear.
  6. From the repo root, run:
    sh
    pnpm changeset add --empty
  7. Edit the generated .changeset/*.md file printed by the command.
    • Put affected packages between the --- lines in changeset format.
    • Use patch or minor values only.
    • Always include orchid-orm when pqb or rake-db are affected.
    • After the second ---, add a blank line and a 1-2 sentence description ending with (#<issue-number>).
  8. Before committing, print the generated outputs and ask for confirmation.
    • If BREAKING_CHANGES.md was changed, print the new section that was added.
    • Print the full generated .changeset/*.md file content.
    • Ask the user to confirm committing; do not commit without confirmation.
  9. Stage and commit:
    • Run git add -A; include all changed files, even files not changed by this agent.
    • Commit with exactly the same message as the changeset description, including (#<issue-number>).
Show full SKILL.md (92 more words)Show less

Quick Reference

SituationRelease type
New functionalitypatch
Contract-preserving extensionpatch
Backward-compatibility gapminor
pqb or rake-db affectedInclude orchid-orm
pqb or rake-db is minororchid-orm is minor

Examples

Prompt changeset 611 1 means read changes/611*/1*/spec.md.

Example changeset file:

md
---
'orchid-orm': minor
'pqb': patch
---

Fix selecting relation when deleting a record (#708)

Common Mistakes

  • Do not classify new functionality as minor; it is patch unless compatibility is not preserved.
  • Do not forget orchid-orm when pqb or rake-db are affected.
  • Do not invent an issue number. Ask the user if it is unknown.
  • Do not alter the commit message; it must exactly match the changeset description.

© romeerez, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/changeset of romeerez/orchid-orm.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit de54a3b

Compare with similar skills

Changeset next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Changeset compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Changeset this skillromeerez/orchid-orm543—~945Automated safety check: PassMIT
Content Create Hero Imageprisma/web1.1k—~6.9kAutomated safety check: PassNone
Sea Orm 2FlyinPancake/yoink112—~2.9kAutomated safety check: PassApache-2.0
Prisma Client APIcurvenote/curvenote1692 repos~1.6kAutomated safety check: PassMIT
DB Migratesimstudioai/sim30k—~2kAutomated safety check: PassApache-2.0
DB Migrationskurealnum/dotfiles290—~820Automated safety check: PassNone

Similar skills

  • Content Create Hero Image

    prisma/web

    Official

    A skill your agent uses when the operator wants a hero or meta image for a Prisma blog post; asks to create or generate a blog hero, cover, social card, Open Graph, or YouTube image; mentions cover…

    1.1k GitHub stars~6.9k tokensUpdated today
    DatabasesAuto-check passed

  • Sea Orm 2

    FlyinPancake/yoink

    Expert guidance for SeaORM 2.0, Rust's async ORM with strongly-typed columns, nested ActiveModels, Entity Loader API, and entity-first workflow.

    112 GitHub stars~2.9k tokensUpdated 3 days ago
    DatabasesAuto-check passed

  • Prisma Client API

    curvenote/curvenote

    Prisma Client API reference covering model queries, filters, operators, and client methods.

    169 GitHub starsUsed in 2 repos~1.6k tokens
    DatabasesAuto-check passed

  • DB Migrate

    simstudioai/sim

    Author or review a Drizzle DB migration for zero-downtime safety — expand/contract phasing, backward-compatibility with the deployed app version, and writing the -- migration-safe acknowledgment the…

    30k GitHub stars~2k tokensUpdated today
    DatabasesAuto-check passed

  • DB Migrations

    kurealnum/dotfiles

    A skill your agent uses when generating or regenerating Drizzle migration files, changing database schema tables or columns, resolving migration sequence conflicts after rebase, reviewing migration…

    290 GitHub stars~820 tokensUpdated 5 mo ago
    DatabasesAuto-check passed

  • Change Database Schema

    martin-ueding/geo-activity-playground

    How to change the SQLAlchemy data model and generate the matching Alembic migration.

    100 GitHub stars~225 tokensUpdated 10 days ago
    DatabasesAuto-check passed

More from romeerez/orchid-orm

All 13 skills in this repo

  • Spec

    romeerez/orchid-orm

    A skill your agent uses when the user prompts "write spec" or "make spec".

    543 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Task List

    romeerez/orchid-orm

    A skill your agent uses when user asks to write a task list, not to do a task

    543 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Type Optimizer

    romeerez/orchid-orm

    A skill your agent uses when need to optimize TypeScript types.

    543 GitHub stars~798 tokensUpdated today
    Auto-check passed

  • Code Doc

    romeerez/orchid-orm

    A skill your agent uses when the user prompts "code doc" to create or update internal Orchid ORM code documentation from changes/ specs, short-code feature folders, or existing implementation code.

    543 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Ideas

    romeerez/orchid-orm

    A skill your agent uses when the user prompts "write ideas" or "make ideas".

    543 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Implemenation Note

    romeerez/orchid-orm

    A skill your agent uses when the user prompts "implementation note" for an existing change idea.

    543 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Categories

Questions about Changeset

How do I install Changeset in Claude Code?

Run `npx skills add romeerez/orchid-orm --skill changeset -a claude-code`. Or copy the skill folder (.agents/skills/changeset in romeerez/orchid-orm) into .claude/skills/changeset in your project. Claude Code loads it when a task matches its description.

How do I install Changeset in Codex?

Run `npx skills add romeerez/orchid-orm --skill changeset -a codex`. Or copy the skill folder (.agents/skills/changeset in romeerez/orchid-orm) into .agents/skills/changeset in your project. Codex loads it when a task matches its description.

Can I use Changeset in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add romeerez/orchid-orm --skill changeset -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changeset, .gemini/skills/changeset, .github/skills/changeset and .opencode/skills/changeset in your project.

What does Changeset need to run?

Going by SKILL.md and its folder, Changeset needs the command-line tools its instructions call (pnpm, git and changeset).

Does Changeset access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Changeset safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Changeset use?

Changeset is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Changeset use?

About 945 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Changeset?

Skills that share tags, products or a category with Changeset: Content Create Hero Image (prisma/web, 1.1k stars), Sea Orm 2 (FlyinPancake/yoink, 112 stars), Prisma Client API (curvenote/curvenote, 169 stars) and DB Migrate (simstudioai/sim, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changeset?

romeerez (a GitHub user) maintains it in romeerez/orchid-orm, which has 543 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

Source: romeerez/orchid-orm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.