agentleFS
tuanductrantuanductran/hr-skills/.agents/skills/changeset/SKILL.md

changeset

Skill58 starsChanged 2 months agoMITView on GitHub

Use when determining whether a pull request requires a changeset, selecting the appropriate version bump (patch, minor, or major), or writing a `.changeset/*.md` entry for the hr-skills repository.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use walkthrough, turborepo and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MSILycanthropySkill

    walkthrough

    Explore and visualize codebase architecture. Use when asked to "walk me through", "show how X works", "explain the flow", "diagram the architecture", or understand how components interact.

    Also in 3 projects that use this

  • VercelSkill

    turborepo

    Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries.

    Also in 3 projects that use this

  • anasahmed07Skill

    better-auth-best-practices

    Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

    Also in 3 projects that use this

  • SentrySkill

    deslop

    Strip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

  • GoogleSkill

    improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

25 rules. 0 are common, 21 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 21

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Use this skill whenever a pull request introduces user-visible changes that should be included in the next release of the hr-skills …

    line 11
  2. Distinctive:

    Do not create a changeset for internal-only work that has no effect on repository users.

    line 15
  3. Distinctive:

    Before creating a changeset, inspect the pull request and classify the changes.

    line 21
  4. Distinctive:

    Create a changeset for changes such as:

    line 25
  5. Distinctive:

    Do not create a changeset for work such as:

    line 40
  6. Distinctive:

    When uncertain, prefer consistency with previous releases and existing changesets in the repository.

    line 51
  7. Distinctive:

    Follow the interactive prompts or edit the generated file inside:

    line 63
  8. Distinctive:

    Do not modify the YAML frontmatter format.

    line 79
  9. Distinctive:

    Use the exact package name defined by the repository.

    line 81
  10. Distinctive:

    Use for backward-compatible fixes and small improvements.

    line 89
  11. Distinctive:

    Use for new functionality that is backward compatible.

    line 105
  12. Distinctive:

    Use for breaking changes.

    line 121
  13. Distinctive:

    Write concise release notes.

    line 141
  14. Distinctive:

    Prefer one to three short sentences.

    line 142
  15. Distinctive:

    Use clear, direct language.

    line 143
  16. Very specific:

    Keep descriptions suitable for inclusion in CHANGELOG.md.

    line 145
  17. Distinctive:

    When appropriate, reference the GitHub issue.

    line 193
  18. Distinctive:

    Write long release notes.

    line 222
  19. Very specific:

    Add Markdown headings inside the description except #### or lower if absolutely necessary.

    line 223
  20. Distinctive:

    Verify a changeset is actually required.

    line 231
  21. Distinctive:

    Verify the selected version bump is correct.

    line 232
  22. Distinctive:

    Verify the package name is correct.

    line 233
  23. Distinctive:

    Verify the description is concise and user-facing.

    line 234
  24. Very specific:

    Verify the generated file is located inside .changeset/.

    line 236
  25. Distinctive:

    Do not edit generated changelog files manually.

    line 238

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Changeset

Purpose

Use this skill whenever a pull request introduces user-visible changes that should be included in the next release of the hr-skills repository.

A changeset records release notes, determines semantic version bumps, and drives CHANGELOG.md generation through Changesets.

Do not create a changeset for internal-only work that has no effect on repository users.


Decision Process

Before creating a changeset, inspect the pull request and classify the changes.

A changeset is required

Create a changeset for changes such as:

  • New skills.
  • New prompts.
  • New examples.
  • New generators.
  • New validators.
  • New build capabilities.
  • New CLI functionality.
  • Bug fixes affecting repository behavior.
  • User-visible documentation improvements that change repository capabilities.
  • Any change that should appear in release notes.

A changeset is usually not required

Do not create a changeset for work such as:

  • Typo fixes.
  • Markdown formatting.
  • README wording improvements.
  • Internal refactoring.
  • Code movement without behavior changes.
  • Test-only changes.
  • CI configuration updates that do not affect released functionality.
  • Comments or cleanup work.

When uncertain, prefer consistency with previous releases and existing changesets in the repository.


Create a Changeset

Generate a new changeset:

bun run changeset

Follow the interactive prompts or edit the generated file inside:

.changeset/

A typical file looks like:

---
"hr-skills": patch
---

Added support for validating duplicate skill names during repository validation.

Do not modify the YAML frontmatter format.

Use the exact package name defined by the repository.


Choose the Correct Version Bump

patch

Use for backward-compatible fixes and small improvements.

Examples:

  • Bug fixes.
  • Prompt improvements.
  • Example improvements.
  • Validator fixes.
  • Tooling corrections.
  • Content corrections.
  • Small enhancements that do not introduce new functionality.

minor

Use for new functionality that is backward compatible.

Examples:

  • New skill.
  • New prompt library.
  • New examples.
  • New validator.
  • New CLI command.
  • New build capability.
  • New repository feature.

major

Use for breaking changes.

Examples:

  • Breaking changes to SKILL.md format.
  • Breaking package API changes.
  • Folder layout changes requiring migration.
  • Removed repository functionality.
  • Incompatible validator behavior.
  • Repository architecture changes requiring user action.

Writing Guidelines

A good changeset explains what changed and why it matters, not how it was implemented.

General Rules

  • Focus on user-visible outcomes.
  • Write concise release notes.
  • Prefer one to three short sentences.
  • Use clear, direct language.
  • End every sentence with a period.
  • Keep descriptions suitable for inclusion in CHANGELOG.md.

Use Past Tense

Describe completed work using past tense.

Examples:

Added a new HR analytics skill.
Fixed duplicate validation logic.
Updated the onboarding examples.

Describe Outcomes

Prefer:

Added validation for duplicate skill names.

Instead of:

Modified validator.ts.

Release notes should describe the effect of the change, not the implementation details.


New Skills

Example:

Added a new `hr-virtual-onboarding` skill covering remote onboarding workflows, manager checklists, and AI-assisted onboarding prompts.

Bug Fixes

When appropriate, reference the GitHub issue.

Example:

Fixed #42 by correcting turnover calculation guidance in the HR analytics content.

Tooling

Example:

Updated repository validation to require prompts and examples for Full-tier skills.

Avoid

Do not:

  • Copy commit messages.
  • List every modified file.
  • Describe internal refactoring.
  • Include implementation details.
  • Repeat repository structure.
  • Write long release notes.
  • Add Markdown headings inside the description except #### or lower if absolutely necessary.

Validation Checklist

Before finishing:

  • Verify a changeset is actually required.
  • Verify the selected version bump is correct.
  • Verify the package name is correct.
  • Verify the description is concise and user-facing.
  • Verify Markdown formatting.
  • Verify the generated file is located inside .changeset/.

Do not edit generated changelog files manually.


References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.