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
- iangregsondev/agent-skillstheir own version, first seen Nov 16, 2026
- getlien/lientheir own version, first seen Nov 15, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
- louisbrulenaudet/monorepo-templatetheir own version, first seen Oct 29, 2026
- frappe/frappe-uitheir own version, first seen Oct 17, 2026
- reactive/data-clienttheir own version, first seen Oct 9, 2026
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.
MSILycanthropySkillwalkthrough
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
VercelSkillturborepo
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
anasahmed07Skillbetter-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
Also in 3 projects that use this
SentrySkilldeslop
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 CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
GoogleSkillimprove-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
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- withastro/astro★ 64ksame name
- biomejs/biome★ 26ksame name
- udecode/plate★ 17ksame name
- reactive/data-client★ 2ksame name
- whitphx/stlite★ 1.7ksame name
- frappe/frappe-ui★ 1.1ksame name
- deadlock-mod-manager/deadlock-mod-manager★ 617same name
- MaxGfeller/open-harness★ 611same name
- udecode/better-convex★ 453same name
- yamcodes/arkenv★ 151same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- biomeSkill
- bunSkill
- clackSkill
- dry-refactoringSkill
- github-awesome-copilot-git-commitSkill
- hr-root-router-maintainingSkill
- hr-skills-maintainingSkill
- humanizerSkill
- jscpdSkill
- markdownSkill
- pdfSkill
- skill-vetterSkill
- turboSkill
- typescriptSkill
- valibotSkill
- hr-skillsSkill
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
- Very specific: line 11
Use this skill whenever a pull request introduces user-visible changes that should be included in the next release of the hr-skills …
- Distinctive: line 15
Do not create a changeset for internal-only work that has no effect on repository users.
- Distinctive: line 21
Before creating a changeset, inspect the pull request and classify the changes.
- Distinctive: line 25
Create a changeset for changes such as:
- Distinctive: line 40
Do not create a changeset for work such as:
- Distinctive: line 51
When uncertain, prefer consistency with previous releases and existing changesets in the repository.
- Distinctive: line 63
Follow the interactive prompts or edit the generated file inside:
- Distinctive: line 79
Do not modify the YAML frontmatter format.
- Distinctive: line 81
Use the exact package name defined by the repository.
- Distinctive: line 89
Use for backward-compatible fixes and small improvements.
- Distinctive: line 105
Use for new functionality that is backward compatible.
- Distinctive: line 121
Use for breaking changes.
- Distinctive: line 141
Write concise release notes.
- Distinctive: line 142
Prefer one to three short sentences.
- Distinctive: line 143
Use clear, direct language.
- Very specific: line 145
Keep descriptions suitable for inclusion in CHANGELOG.md.
- Distinctive: line 193
When appropriate, reference the GitHub issue.
- Distinctive: line 222
Write long release notes.
- Very specific: line 223
Add Markdown headings inside the description except #### or lower if absolutely necessary.
- Distinctive: line 231
Verify a changeset is actually required.
- Distinctive: line 232
Verify the selected version bump is correct.
- Distinctive: line 233
Verify the package name is correct.
- Distinctive: line 234
Verify the description is concise and user-facing.
- Very specific: line 236
Verify the generated file is located inside .changeset/.
- Distinctive: line 238
Do not edit generated changelog files manually.
“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.
Files
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 changesetFollow 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
AGENTS.mdREADME.mddocs/engineering/format.md.changeset/CHANGELOG.md- Changesets documentation: https://github.com/changesets/changesets/tree/main/docs
- Conventional Commits: https://www.conventionalcommits.org/
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
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.

