prepare-release Skill
Prepare a release for the JavaScript Feature Management packages. Use when user mentions release preparation, version bump, creating merge PRs, preview release, or stable release for this project. Published by microsoft in FeatureManagement-JavaScript.
Decision snapshot
Is this a fit?
Browser automation, 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 prepare-release Skill?
Prepare a release for the JavaScript Feature Management packages. Use when user mentions release preparation, version bump, creating merge PRs, preview release, or stable release for this project. Published by microsoft in FeatureManagement-JavaScript. 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
- Browser automation
- Browser automation use cases
Declared skill metadata
- Source file: .github/skills/prepare-release/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use prepare-release Skill
- Use it for browser automation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/FeatureManagement-JavaScript
- Skill file: .github/skills/prepare-release/SKILL.md
What it does
Prepare a release for the JavaScript Feature Management packages. Use when user mentions release preparation, version bump, creating merge PRs, preview release, or stable release for this project.
Skill instructions
Prepare Release This skill automates the release preparation workflow for the JavaScript Feature Management project. When to Use This Skill Use this skill when you need to: - Bump the package version for a new stable or preview release - Create merge PRs to sync branches (main → release, preview → release) - Prepare all the PRs needed before publishing a new release Background Repository Information - GitHub Repo: https://github.com/microsoft/FeatureManagement-JavaScript - Packages: - @microsoft/feature-management - @microsoft/feature-management-applicationinsights-browser - @microsoft/feature-management-applicationinsights-node Branch Structure - main – primary development branch for stable releases - preview – development branch for preview releases - release/v{major} – release branch (e.g., release/v2) Version Files The version must be updated in all 7 files simultaneously. Some files have multiple locations that need updating: 1. src/feature-management/src/version.ts – line 4: expo
Verified compatibility and discovery
Frequently asked questions
What is prepare-release?
prepare-release is a open-source AI agent skill with Copy skill directory. Prepare a release for the JavaScript Feature Management packages. Use when user mentions release preparation, version bump, creating merge PRs, preview release, or stable release for this project.
Who is prepare-release best for?
prepare-release is best for reusing agent instructions, scripts, and references, browser automation workflows.
How do I install prepare-release?
Install or run prepare-release using Copy skill directory. Check prepare-release for the latest setup command.
Is prepare-release actively maintained?
prepare-release may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
