Manage semantic version updates for claude-mem project. Handles patch, minor, and major version increments following semantic versioning. Updates package.json, marketplace.json, plugin.json, and CLAUDE.md version number (NOT version history). Creates git tags and GitHub releases. Auto-generates CHANGELOG.md from releases.
Use when modifying, proposing, or explaining version numbers, release tags, or upgrade policies in this repo; applies the repo’s epoch semver scheme (see EPOCH_SEMVER.md) and ensures any version changes follow that format.
Analyzes NuGet packages and project dependencies for security and updates
Rust crate and library development patterns covering Cargo.toml for libraries, crate structure, module organization, rustdoc, publishing to crates.io, feature flags, semantic versioning, and API design. Use when creating a Rust library or crate, publishing to crates.io, documenting APIs with rustdoc, or managing library features and versions. This is the specialized skill for Rust library/crate development.
Set up Python project for PyPI publishing with pyproject.toml, src layout, and build scripts. Use when creating a new Python package, setting up for PyPI distribution, or initializing a Python library project.
Manage NuGet/.NET dependencies with enterprise-grade safety: versioning strategy, vulnerability awareness, licensing awareness, and minimizing supply-chain risk. Use when adding/updating packages or changing restore/build behavior.
Create consistent releases with changelogs and version bumping
Set up Docker deployment for Flask applications with Gunicorn, automated versioning, and container registry publishing. Use when dockerizing a Flask app, containerizing for production, or setting up CI/CD with Docker.
Split large Python files into multiple files organized as a package. Use when user says "split this file", "this file is too big", "break this into multiple files", or similar requests for Python (.py) files.
Windows Tauri application packaging skill. Summarizes code changes, updates documentation, commits and merges to main with tag, then creates distribution zip package.
Bump semantic version across all project files (package.json, CLI, README, docs). Use for version updates without full release.
Python package manager and project tooling using uv. Use when working with Python projects, managing dependencies, creating virtual environments, running Python scripts, configuring workspaces/monorepos, or troubleshooting uv issues. Triggers on pyproject.toml projects, uv commands, pip replacement workflows, Python version management, workspace configuration, or CI/CD Python setup.
Set up Python projects using nix/direnv with uv for environment management. Use when creating new Python projects, initializing Python environments, or when the user wants automatic Python virtual environment setup with nix flakes.
Generate standardized Python project structure with pyproject.toml, UV environment, pytest configuration, and workspace-hub compliance. Creates production-ready project scaffolding.
This skill should be used when creating new Python projects or managing Python dependencies. IMPORTANT - uv must ALWAYS be used for any Python-related commands in Python projects (running scripts, installing packages, creating virtual environments, etc.). Never use pip, python directly, or other package managers - always use uv commands (uv run, uv add, uv pip, etc.).
Create a target for haskell application.
Master Python package management with Poetry, dependency resolution, publishing, and project structure
Increment agent version in pyproject.toml. Use when releasing new versions, updating semantic version, or preparing for deployment.
Publish @autumnsgrove/groveengine to npm with proper registry swap workflow. Use when releasing a new version of the engine package to npm.
Create and deploy new versions to Homebrew tap with automatic cask updates
Guidance for developing under a projects managed by pixi. Always use when workspace managed by pixi (have pixi.toml or pixi.lock in root directory.) Covers all you should know while developing under a pixi-based project: pixi environment commands (install, run, shell, add, task), multi-environment management (-e flag, features), task configuration in pixi.toml, dependencies (conda vs PyPI), lock files, and development workflows. Helps with environment setup, package management, running tasks, debugging pixi.toml errors, and production deployment patterns.
SEMO npm 패키지 배포. Use when (1) "npm 배포", "패키지 배포해줘", (2) CLI/MCP 변경 후 배포, (3) "버전 올리고 배포".
Vet new package dependencies before installation. Triggers when adding packages via pip, npm, yarn, or similar package managers. Checks for typosquatting, known vulnerabilities, low adoption (potential supply chain risk), and package metadata anomalies. Use when: - User asks to install a new package - pip install, npm install, yarn add commands detected - requirements.txt or package.json modifications - User asks "is this package safe?" Blocks: Typosquats, critical vulnerabilities Warns: Low adoption, suspicious metadata
