beachball-change-file Skill
How to create a Beachball change file. ONLY use this skill when the user asks to generate change files, before pushing a branch, or before creating a PR. Published by microsoft in lage.
Decision snapshot
Is this a fit?
Developers using lage, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is beachball-change-file Skill?
How to create a Beachball change file. ONLY use this skill when the user asks to generate change files, before pushing a branch, or before creating a PR. Published by microsoft in lage. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using lage
Declared skill metadata
- Source file: .claude/skills/beachball-change-file/SKILL.md
Compatibility and setup
- Install or run with Copy skill directory
When to use beachball-change-file Skill
- Use it for developers using lage.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/lage
- Skill file: .claude/skills/beachball-change-file/SKILL.md
What it does
How to create a Beachball change file. ONLY use this skill when the user asks to generate change files, before pushing a branch, or before creating a PR.
Skill instructions
Beachball is a tool used for managing versioning and changelogs for JS/TS codebases. Every pull request must include a Beachball change file. Change files include the list of packages with public-facing changes in the branch, with the description and semver change type for each package. After the PR is checked in and a release is run, the change files are used to determine version bumps and update changelogs. Beachball normally uses a CLI with an interactive prompt to create change files, but they can also be created manually using the standardized JSON format detailed below. Prerequisites - Deterine the root directory: this is almost always the git root, but the user might specify a different folder. (The root usually contains beachball.config. or .beachballrc. or has a "beachball" key in package.json.) - Determine the package manager for the repo (npm, yarn, pnpm). The example commands below assume yarn, but substitute the appropriate command runner syntax for a different package man
Verified compatibility and discovery
Frequently asked questions
What is beachball-change-file?
beachball-change-file is a open-source AI agent skill with Copy skill directory. How to create a Beachball change file. ONLY use this skill when the user asks to generate change files, before pushing a branch, or before creating a PR.
Who is beachball-change-file best for?
beachball-change-file is best for reusing agent instructions, scripts, and references.
How do I install beachball-change-file?
Install or run beachball-change-file using Copy skill directory. Check beachball-change-file for the latest setup command.
Is beachball-change-file actively maintained?
beachball-change-file may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
