name	release-prep
description	Skill for preparing the project for a release

I want to prepare this project for the next release, which will be {input}. Please do the following:

Run all tests and linting checks
Check for any TODO or FIXME comments that should be addressed before release
Verify all dependencies are up to date and check for known security vulnerabilities
Ensure the build succeeds without warnings

Update version numbers in all relevant files (package.json, go.mod, VERSION files, etc.)
Verify version consistency across the project

Update the changelog to have a summary of the new version. This means you need to condense everything in the unreleased section to only focus on everything that is new or changed since the last release. There should not be any mention of things that have been changed during the unreleased dev-cycle, the changelog should only show the final result for it. The changelog is meant for new users to understand the changes, so while internal changes can be mentioned, they should not be the focus. Ensure that the changelog doesn't get overly verbose, so keep things tight.
Add the release date to the changelog version header
Ensure there is proper user documentation for all changes in the changelog
Update README.md if there are new features or breaking changes that affect usage
Check that all code examples in documentation are current and working
Review and update any installation or upgrade instructions

Verify all CI/CD pipelines are passing
Ensure git tags follow the project's versioning scheme
Check that the repository is clean (no uncommitted changes that should be included)
Review open issues and PRs to ensure nothing critical is being left out

DO NOT commit, tag, or create releases. All changes should be left uncommitted for the user to review. The user will handle:

name	release-prep
description	Skill for preparing the project for a release

I want to prepare this project for the next release, which will be {input}. Please do the following:

Run all tests and linting checks
Check for any TODO or FIXME comments that should be addressed before release
Verify all dependencies are up to date and check for known security vulnerabilities
Ensure the build succeeds without warnings

Update version numbers in all relevant files (package.json, go.mod, VERSION files, etc.)
Verify version consistency across the project

Update the changelog to have a summary of the new version. This means you need to condense everything in the unreleased section to only focus on everything that is new or changed since the last release. There should not be any mention of things that have been changed during the unreleased dev-cycle, the changelog should only show the final result for it. The changelog is meant for new users to understand the changes, so while internal changes can be mentioned, they should not be the focus. Ensure that the changelog doesn't get overly verbose, so keep things tight.
Add the release date to the changelog version header
Ensure there is proper user documentation for all changes in the changelog
Update README.md if there are new features or breaking changes that affect usage
Check that all code examples in documentation are current and working
Review and update any installation or upgrade instructions

Verify all CI/CD pipelines are passing
Ensure git tags follow the project's versioning scheme
Check that the repository is clean (no uncommitted changes that should be included)
Review open issues and PRs to ensure nothing critical is being left out

DO NOT commit, tag, or create releases. All changes should be left uncommitted for the user to review. The user will handle:

release-prep

المزيد من هذا المستودع