Skip to content
Skills Library
Programming · Automation

quickrelease

/quickrelease

Cuts a MooshieUI semver release quickly, skipping bot reviews, pre-commit-checks, and local build validation. Bumps versions, prepends release notes, commits, pushes, creates/merges release PR, and tags the release. Use when the user says /quickrelease or wants a checkless release.

Repository
MooshieUI ↗
Licence
AGPL-3.0
Last repository change
14.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
2
Deprecation

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

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Cuts a MooshieUI semver release quickly, skipping bot reviews, pre-commit-checks, and local build validation. Bumps versions, prepends release notes, commits, pushes, creates/merges release PR, and tags the release. Use when the user says /quickrelease or wants a checkless release.

Original author description

Cuts a MooshieUI semver release quickly, skipping bot reviews, pre-commit-checks, and local build validation. Bumps versions, prepends release notes, commits, pushes, creates/merges release PR, and tags the release. Use when the user says /quickrelease or wants a checkless release.

How it works

  1. Inputs
  2. Windows git (required)
  3. Workflow
  4. Checklist
  5. Mistakes to avoid
Original SKILL.md headings · 153 lines, 660 words
SKILL.md preview
---
name: quickrelease
description: >-
  Cuts a MooshieUI semver release quickly, skipping bot reviews, pre-commit-checks,
  and local build validation. Bumps versions, prepends release notes, commits, pushes,
  creates/merges release PR, and tags the release. Use when the user says /quickrelease or wants a checkless release.
---

# Quick Release (MooshieUI)

Fast-path release: **checkout main → version bump → changelog → push branch → PR → auto-merge → tag → CI**.

This workflow skips all developer hygiene checks, linting, pre-commit hooks, and local build verification. Use it only when the changes are trivial and already verified.

## Inputs

| Field | Default if omitted |
|-------|-------------------|
| Version `X.Y.Z` | Read `package.json`, patch+1 (no `v` prefix in files) |
| Summary | `git log` since last `v*` tag |

## Windows git (required)

```text
git -c core.hooksPath=/dev/null ...
```

Pre-commit hook hangs in PowerShell without this.

## Workflow

### 1. Sync main branch

Ensure you are on a fresh, updated `main` branch before bumping versions:

```powershell
git checkout main
git pull origin main
```

### 1b. Dependency audit [BLOCKING]

The one check this fast path keeps: the tagged **Build & Release** run audits dependencies and fails on any advisory published since the last merge.

```powershell
& "$env:ProgramFiles\Git\bin\bash.exe" scripts/audit-deps.sh
```

On a vulnerability, update the crate (or the parent that pulls it in, `cargo tree -i <crate>@<version>`) on a normal PR first, then release.

### 2. Version bump (all three must match)

Update version in:

| File | Field |
|------|-------|
| `package.json` | `"version": "X.Y.Z"` |
| `src-tauri/Cargo.toml` | `version = "X.Y.Z"` under `[package]` |
| `src-tauri/tauri.conf.json` | `"version": "X.Y.Z"` |

### 3. Changelog files

Prepend to **both** `docs/RELEASE_NOTES.md` and `CHANGELOG.md`:

```markdown
## What's New in vX.Y.Z

### Fixes and maintenance
- Detail

---

## What's New in vPREVIOUS
```

`CHANGELOG.md`: new section goes directly under `# Changelog`.

### 4. Create and push release branch

```powershell
git checkout -b release/vX.Y.Z
git add -A
git -c core.hooksPath=/dev/null commit -m "vX.Y.Z: Quick release"
git -c core.hooksPath=/dev/null push -u origin release/vX.Y.Z
```

### 5. Create Pull Request

```powershell
gh pr create --base main --head release/vX.Y.Z --title "vX.Y.Z: Quick release" --body "<bullet list of changes>"
```

### 6. Merge PR

If branch checks are green or can be bypassed:
```powershell
gh pr merge <PR_NUMBER> --squash --delete-branch
```
If branch policy blocks the merge due to pending checks or admin settings, add the `--admin` flag:
```powershell
gh pr merge <PR_NUMBER> --squash --delete-branch --admin
```

### 7. Sync main & Tag

```powershell
git checkout main
git fetch origin main
git reset --hard origin/main
git tag vX.Y.Z
git -c core.hooksPath=/dev/null push origin vX.Y.Z
```

This triggers the **Build & Release** workflow on GitHub Actions.

### 8. Cleanup

```powershell
git fetch --prune origin
```

Prune any stale local branches.

### 9. Wiki pass [user-facing changes only]

Quick releases are usually trivial fixes that need no docs — skip this step then. But if this release adds, renames, or removes a user-facing feature or setting, sync the wiki (a **separate repo**: `https://github.com/Mooshieblob1/MooshieUI.wiki.git`, branch `master`, top-level `*.md`, nav `_Sidebar.md`).

```powershell
git clone https://github.com/Mooshieblob1/MooshieUI.wiki.git <scratch>/MooshieUI.wiki   # outside the main repo
```

Edit the page(s) for each user-facing item in this release's `## What's New in vX.Y.Z` block, **verifying exact UI labels against current code** (`src/lib/locales/en.ts` + the component) — labels get renamed before ship. Match the wiki's concise, present-tense voice. Then:

```powershell
git -c core.hooksPath=/dev/null commit -am "Document vX.Y.Z: <short summary>"
git -c core.hooksPath=/dev/null push origin master
```

No `Co-Authored-By`, no em dashes. Report pages touched (or that the wiki pass was skipped as internal-only).

## Checklist

```
- [ ] Stale release/* branches cleaned up
- [ ] Three version files match X.Y.Z
- [ ] docs/RELEASE_NOTES.md + CHANGELOG.md updated
- [ ] Release PR merged to main
- [ ] Tag vX.Y.Z pushed
- [ ] Release workflow running on GitHub
- [ ] Wiki pass done for user-facing changes (or skipped as internal-only)
```

## Mistakes to avoid

1. Adding `Co-Authored-By` trailers to commits, PR bodies, or comments — never attribute AI assistance in any git or GitHub output
2. Missing one of the three version files
3. `git` without `core.hooksPath=/dev/null` on Windows
4. Tag before PR merge
5. Force-updating tags — use `workflow_dispatch` instead

Versions

RepositoryScoreLicence
This page · Mooshieblob1/MooshieUI100AGPL-3.0
Mooshieblob1/MooshieUI100AGPL-3.0

Database snapshot: 13.11.2026 · package version cc3d5cb8a971 (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

  • 100release
    Cuts a MooshieUI semver release — bumps three version files, updates changelog and release notes, validates build, opens release PR, merges, tags, and triggers Build & Release CI. Use when the user says /release, cut a release, ship vX.Y.Z, or version bump.
  • 100release
    Cuts a MooshieUI semver release — bumps three version files, updates changelog and release notes, validates build, opens release PR, merges, tags, and triggers Build & Release CI. Use when the user says /release, cut a release, ship vX.Y.Z, or version bump.
  • 100chamoji-release
    Cut a release from git history in one command with the chamoji CLI. It picks the semver bump from the commits, adds the CHANGELOG.md section, bumps manifest versions, and makes the release commit and tag (and pushes plus a GitHub release on request). Use it whenever the user…
  • 95release
    Releases a new version of my-skills-anywhere. Bumps the semver version in the plugin manifest, runs the unit tests, the manifest checks and the verify skill, checks commit identities, commits, tags, and pushes only on the owner's explicit yes. Use when asked to release, cut a…
  • 100deploy
    Releases wipnote: runs the quality gates, bumps the version, tags, pushes, and triggers the GitHub release pipeline. Use when asked to deploy, release, publish, or ship a new wipnote version.
  • 90release
    Cut a harness-eval release - bump the version in the three manifest fields and the README version badge, update CHANGELOG (EN+KO), tag. Use only when the user asks to release.

Feedback and reports

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