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

Create Changeset

by techwithanirudh in techwithanirudh/coolify-tweaks

Analyze git changes and create changesets for package releases.

MITAuto-check passedDevelopment

Install Create Changeset

skills CLI
$ npx skills add techwithanirudh/coolify-tweaks --skill create-changeset -a claude-code

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

GitHub CLI
$ gh skill install techwithanirudh/coolify-tweaks create-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/techwithanirudh/coolify-tweaks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-changeset .claude/skills/create-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
create-changeset
GitHub stars
173
Token cost
~1.4k tokens
SKILL.md length
626 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Analyze git changes and create changesets for package releases.

  • Works in 5 steps: Check Current State → Analyze Changes → Determine Version Bump Type → …
  • Preparing pull requests
  • SKILL.md covers Purpose, When to Invoke, Pre-execution Validation and Implementation Steps
  • Calls git

What it does

Create Changeset is an agent skill from techwithanirudh/coolify-tweaks. Analyze git changes and create changesets for package releases. Use when preparing pull requests, creating PRs, when branch has commits ready for review, or when user mentions changeset or version bump.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests and Git workflow. It works with Git. The repository describes itself as: A userstyle that enhances Coolify's UI by applying opinionated tweaks, spacing, colors, and layout fixes, to make the UI more polished and user-friendly. The licence is MIT.

When your agent uses it

  • Preparing pull requests
  • Branch has commits ready for review
  • User mentions changeset

Example prompts

  • “/create-changeset”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git:*), Bash(pnpm:*), Read, Write

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Check Current State
  2. Analyze Changes
  3. Determine Version Bump Type
  4. Generate Changeset
  5. Verify and Commit

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git:*)
    • Bash(pnpm:*)
    • Read
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use 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

Create Changeset loads about 1.4k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 626 words of instructions outside code blocks.

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

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 techwithanirudh/coolify-tweaks at commit f7f6e31, republished under its MIT licence (© techwithanirudh). 626 words, ~1,363 tokens.

Download SKILL.mdSave it as .claude/skills/create-changeset/SKILL.md (or your agent's skills folder).
name
create-changeset
description
Analyze git changes and create changesets for package releases. Use when preparing pull requests, creating PRs, when branch has commits ready for review, or when user mentions changeset or version bump.
allowed-tools
Bash(git:*), Bash(pnpm:*), Read, Write

Create Changeset Skill

Purpose

This skill automatically analyzes branch changes and creates appropriate changesets for package releases in this monorepo. It examines git history, determines version bump types based on Conventional Commits, and generates properly formatted changeset files.

When to Invoke

Automatically invoke this skill when:

  • User is preparing to create a pull request
  • User mentions "PR", "pull request", or "ready for review"
  • Branch has commits ready for review
  • User explicitly mentions "changeset" or "version bump"

Do NOT invoke when:

  • User is only pushing changes without creating a PR
  • Only documentation files have changed (README, .md files)
  • Only CI/CD configuration has changed (.github/workflows/)
  • Only development tool configuration has changed (eslint, prettier, etc.)
  • Commits are only docs:, chore:, ci:, or test: types that don't affect packages

Pre-execution Validation

Before creating a changeset, check if a changeset file already exists for the current changes:

  • Look for .changeset/*.md files (excluding README.md)
  • If exists, ask user: "A changeset already exists. Create another one?"

Repository note: Only the @repo/style package currently publishes via changesets. No other workspace packages emit changeset-based releases, so focus analysis on apps/style/ files and the surrounding tooling that affects it.

Implementation Steps

1. Check Current State
  • Run git fetch --tags, then determine the latest release tag (git tag --list 'v*' --sort=-v:refname | head -n1).
  • Use git log <latest-tag>..HEAD (or origin/main..<latest-tag> if needed) to verify there are commits to release.
  • If no tags exist, fall back to git log main..HEAD and explain why you're using the branch range.
  • Stop if there are no commits since the latest tag.
2. Analyze Changes
  • Diff against the latest tag (git diff <latest-tag>..HEAD) to inspect committed changes.
  • Keep the focus on apps/style/ and its build tooling, since @repo/style is the only changeset-published package.
  • Summaries: use git log <latest-tag>..HEAD --oneline for Conventional Commit intents.
  • Only mention files outside apps/style/ if they clearly affect the generated CSS.
Show full SKILL.md (318 more words)Show less
3. Determine Version Bump Type

Analyze commit messages following Conventional Commits 1.0.0 format:

  • major: Contains BREAKING CHANGE in commit body, or breaking changes detected in code
    • API signature changes
    • Removed exports or features
    • Incompatible behavior changes
  • minor: Starts with feat: or feat(scope): - new features (backward compatible)
    • New components or functionality
    • New props or options (with defaults)
    • New exports
  • patch: Starts with fix: or fix(scope): - bug fixes and minor improvements
    • Bug fixes
    • Performance improvements
    • Minor style updates
  • skip: Other types (chore:, docs:, ci:, test:) typically don't require changesets unless they affect package functionality

Review actual code changes to confirm the appropriate version bump. When in doubt between minor and patch, prefer patch for safety.

If the version bump is ambiguous or unclear:

  • Ask user for clarification
  • Explain the reasoning behind the suggested bump type
  • Allow user to override the suggestion

If all commits are types that don't require changesets (docs:, chore:, ci:, test:), exit early without creating a changeset.

4. Generate Changeset

Create a changeset file with a descriptive filename in .changeset/ directory.

Filename format:

  • Use kebab-case with .md extension
  • Examples: .changeset/add-new-button.md, .changeset/fix-layout-bug.md, .changeset/update-icon-props.md

File content format:

markdown
---
"@repo/package-name": major|minor|patch
---

Clear description of the change

Example for single package:

markdown
---
"@repo/style": minor
---

Add new Button variant for secondary actions

Example for multiple packages:

markdown
---
"@repo/style": minor
"@repo/docs": patch
---

- style: Add new Button variant for secondary actions
- dosc: Add new docs page for contributing

Important guidelines:

  • The description should be user-friendly as it will appear in CHANGELOG
  • Use the same language as the commit messages (Japanese or English). If commit messages are mixed, prefer Japanese.
  • Split changesets into separate files when the same package has changes with different purposes (e.g., new feature + bug fix, breaking change + internal refactoring)
  • This creates individual top-level items in release notes, making it easier for readers to understand the intent of each change
  • Example: Create .changeset/add-secondary-button.md for a new feature and .changeset/fix-button-layout.md for a bug fix, even if both target the same package
5. Verify and Commit

Display the generated changeset for review:

  • Show the file path
  • Show the file content
  • Confirm it accurately reflects the changes

Once verified, commit the changeset file:

bash
git add .changeset/<filename>.md
git commit -m "chore: add changeset"

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

Files

Just SKILL.md in .agents/skills/create-changeset of techwithanirudh/coolify-tweaks.

Open the folder on GitHubat commit f7f6e31

Compare with similar skills

Create 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.

Create Changeset compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Changeset this skilltechwithanirudh/coolify-tweaks173—~1.4kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Git Branch Namingmakeplane/plane61k—~594Automated safety check: PassAGPL-3.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Git Branch Naming

    makeplane/plane

    Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.

    61k GitHub stars~594 tokensUpdated today
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    61k GitHub stars~824 tokensUpdated today
    DevelopmentAuto-check passed

Works with

Categories

Questions about Create Changeset

What does Create Changeset do?

Analyze git changes and create changesets for package releases. Create Changeset is an agent skill from techwithanirudh/coolify-tweaks. Analyze git changes and create changesets for package releases.

When should I use Create Changeset?

Create Changeset fits situations like: preparing pull requests; branch has commits ready for review; user mentions changeset.

How do I install Create Changeset in Claude Code?

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

How do I install Create Changeset in Codex?

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

Can I use Create 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 techwithanirudh/coolify-tweaks --skill create-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/create-changeset, .gemini/skills/create-changeset, .github/skills/create-changeset and .opencode/skills/create-changeset in your project.

What does Create Changeset need to run?

Going by SKILL.md and its folder, Create Changeset needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash(git:*), Bash(pnpm:*), Read, Write.

Does Create 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 Create 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 Create Changeset use?

Create 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 Create Changeset use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Create Changeset?

Skills that share tags, products or a category with Create Changeset: Finishing a Development Branch (obra/superpowers, 296k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Git Branch Naming (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Changeset?

techwithanirudh (a GitHub user) maintains it in techwithanirudh/coolify-tweaks, which has 173 GitHub stars. The repository was last updated on July 31, 2026.

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