Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
prepare-package-release
prepare-package-release
alizharb/agent-skills
claude-code
release
changelog
semver
git-tags
ci
github-releases
validation

Use when preparing a package release with changelog, semantic versioning, validation, tags, and GitHub release notes.

Install
php artisan boost:add-skill alizharb/agent-skills

Save this content to: .claude/skills/prepare-package-release/SKILL.md

# Prepare Package Release

## When To Use

Use this skill before tagging a package version.

## Workflow

1. Inspect the latest tags, changelog, composer metadata, and branch status.
2. Confirm the next version follows semantic versioning.
3. Run formatting, tests, static analysis, and package-specific validators.
4. Move relevant changelog entries from `Unreleased` into the release version and date.
5. Commit release metadata separately when appropriate.
6. Create an annotated or lightweight tag matching the repository convention.
7. Push `main` and the tag.
8. Check GitHub Actions for the release commit and tag.
9. Draft release notes from the changelog.

## Verification

- Confirm `git tag --points-at HEAD` includes the release tag.
- Confirm remote tags include the new tag.
- Confirm CI is green.

## Common Mistakes

- Tagging before updating the changelog.
- Tagging the wrong commit.
- Forgetting to push the tag.

Prepare Package Release

When To Use

Use this skill before tagging a package version.

Workflow

  1. Inspect the latest tags, changelog, composer metadata, and branch status.
  2. Confirm the next version follows semantic versioning.
  3. Run formatting, tests, static analysis, and package-specific validators.
  4. Move relevant changelog entries from Unreleased into the release version and date.
  5. Commit release metadata separately when appropriate.
  6. Create an annotated or lightweight tag matching the repository convention.
  7. Push main and the tag.
  8. Check GitHub Actions for the release commit and tag.
  9. Draft release notes from the changelog.

Verification

  • Confirm git tag --points-at HEAD includes the release tag.
  • Confirm remote tags include the new tag.
  • Confirm CI is green.

Common Mistakes

  • Tagging before updating the changelog.
  • Tagging the wrong commit.
  • Forgetting to push the tag.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console