Skip to content
Skills Library
Programming · Automation

package-release

/package-release

Cut a release of kayedspace/laravel-mcp-bridge. Use when asked to tag a version, prepare release notes, or check whether something is safe to release.

Licence
MIT
Last repository change
06.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Cut a release of kayedspace/laravel-mcp-bridge. Use when asked to tag a version, prepare release notes, or check whether something is safe to release.

Original author description

Cut a release of kayedspace/laravel-mcp-bridge. Use when asked to tag a version, prepare release notes, or check whether something is safe to release.

How it works

  1. Before tagging
  2. Versioning
  3. The notes
Original SKILL.md headings · 49 lines, 349 words
SKILL.md preview
---
name: package-release
description: >
  Cut a release of kayedspace/laravel-mcp-bridge. Use when asked to tag a
  version, prepare release notes, or check whether something is safe to
  release.
license: MIT
---

# Releasing

## Before tagging

```bash
composer test
```

That is the whole gate, and it is what CI runs. Then check the three things CI
cannot:

1. **The dist archive.** `git archive --format=tar HEAD | tar -t` should list
   `src`, `config`, `database`, `resources`, `composer.json`, the README and
   the LICENSE, and nothing else. A development directory that slipped past
   `.gitattributes` ships to every consumer.
2. **The manifest format.** If `ManifestRepository::VERSION` changed, a
   compiled manifest from the previous release will not be read. That is a
   breaking change for anyone who caches the manifest in their build, and it
   belongs in the release notes.
3. **Config keys.** A key that was renamed or removed silently changes
   behaviour for an application that published the config file before. Keep
   reading the old key for one minor version and say so, or call it breaking.
4. **Migrations.** Before the first tag a shipped migration may be edited in
   place. From the first tag on, every schema change is a new migration file,
   because an application that already ran the old one will never run it
   again. `git log --since=<last tag> -- database/migrations` showing a
   modified file rather than an added one is a release blocker.

## Versioning

Until 1.0 the public API may change, which is stated in the README. Even so:

- A new attribute, source, command or config key is a minor.
- A changed default that exposes more than it did before is **breaking**, no
  matter how small. Exposure defaults are the promise this package makes.
- A changed refusal, a stricter check or a narrower default is a minor, and
  goes in the notes so nobody debugs it as a regression.

## The notes

There is no changelog file. Release notes live on the GitHub release, built
from pull request labels through `.github/release.yml`: `breaking`,
`enhancement`, `bug`, `documentation`, `dependencies`. The first release has
no notes about changes, because there is nothing before it to change from.

Write the summary for someone upgrading, not for someone reading the diff.
What changes for an application that does nothing? What must they change?

Versions

RepositoryScoreLicence
This page · kayedspace/laravel-mcp-bridge100MIT
peteonrails/voxtype100MIT
dannote/dot-pi100MIT

Database snapshot: 13.11.2026 · package version 674af230c440 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90Release cut
    Trigger the Release workflow, watch it, and verify the tag, release notes and attached artifacts. Use when the user asks to cut, publish or ship a release.
  • 100prepare-release
    Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.
  • 100mcp-bridge
    Expose a Laravel application's existing routes, Artisan commands, jobs, actions and models to AI agents as MCP tools with kayedspace/laravel-mcp-bridge. Use when asked to make an application agent-accessible, to add or remove a tool, to open a model's relations to agents, to…
  • 100create-release
    Cut a new release of the Implicits library — draft categorized release notes from changes since the last tag, create a draft GitHub release, and trigger the Release workflow that tests, tags, and publishes. Use when asked to release implicits, cut/create a release, or via /create-release <version>.
  • 100release
    Cut a tagged, signed, notarized GitHub release of iMessage Bridge with scripts/release.sh. Use when the user asks to release, ship, tag or publish a version (e.g. "release 0.2.0", "cut a patch release", "/release minor").
  • 100create-release-checklist
    Generate a comprehensive release checklist when the user asks to prepare a release, create a release plan, or ship a version

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.