Automated summary
Automates the steps to prepare a new release: updating version number, changelog, and building the package.
Strengths
- Ensures consistency across version files (pyproject.toml, __init__.py)
- Structures the CHANGELOG with properly dated sections
- Cleans and rebuilds distribution files reliably
Limitations
- Specifically designed for Python projects using pyproject.toml
- Does not publish the release (preparation only)
- Requires user to provide the version number
When you need to prepare a new version of a Python package before publishing.
If you're looking for a complete publishing tool (use a CI/CD workflow instead).
Security analysis
SafeThe skill only runs standard Python build commands and a targeted rm for cleanup. No exfiltration, no disabling of safety, no obfuscation.
No concerns found
How this analysis is madeExamples
Prepare a release for version 0.4.1.Run the release preparation steps: update version to 1.0.0, update changelog, and build the package.name: prep_release description: バージョン更新、CHANGELOG整備、パッケージビルドなど、リリース前の準備を行う
Prepare Release
This skill automates the steps required to prepare a new version release.
Instructions
-
Update Version:
- Ask the user for the new version number (e.g.
0.4.1). - Update
versioninpyproject.toml. - Update
__version__variable ingwexpy/__init__.pyif it exists.
- Ask the user for the new version number (e.g.
-
Update Changelog:
- Read
CHANGELOG.md. - Create a new header for the new version with the current date.
- Move "Unreleased" changes under this new header.
- Read
-
Build Package:
- Clean old distribution files:
rm -rf dist/ build/ *.egg-info. - Run build command:
python -m build. - Check if correct
.tar.gzand.whlfiles are created indist/.
- Clean old distribution files:
-
Verify:
- (Optional) Run
twine check dist/*to verify metadata validation iftwineis available.
- (Optional) Run
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/release-preparation-mmio71u5/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/release-preparation-mmio71u5' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/release-preparation-mmio71u5/download' --output '.skill-downloads/release-preparation-mmio71u5/SKILL.md.part' && mv '.skill-downloads/release-preparation-mmio71u5/SKILL.md.part' '.skill-downloads/release-preparation-mmio71u5/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/release-preparation-mmio71u5/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.