- 📁 agents/
- 📄 SKILL.md
- 📄 use_cases.yaml
Track which stacks use a specific Pulumi package and at what versions, or upgrade a stack to the latest version of a package. Use when users ask about package version tracking, outdated package versions across stacks, upgrade candidates, or package usage audits. Also use when users want to upgrade/update a specific package version in a stack or project. Do NOT use for general infrastructure creation, resource provisioning, or questions about how to use a package.
Bump the FutureSearch SDK version across all files. Use when releasing a new SDK version, updating version numbers, or the user says bump version, release, version bump.
Increment the package version, commit the release, create a matching version tag, and push main plus the tag. Use when releasing this repo, publishing the package, bumping the version, tagging a release, or when the user asks to "release", "bump ver", "tag", or "push tags".
Tend release workflow. Use when user asks to "do a release", "release a new version", "cut a release", or wants to publish a new version to PyPI.
> **Last updated:** 2026-03-16 | **Agency version:** 2026.3.14.2
Publish a new version of klaude-code to PyPI. This skill handles version bumping, changelog updates, git tagging, and package publishing. Use when the user wants to release a new version.
Flip the snap spec default version. Updates all files that reference the current version — constants, docs config, SKILL.md files, template, and llms.txt.
- 📁 tools/
- 📁 workflows/
- 📄 SKILL.md
Automate the full release workflow for syllago. USE WHEN creating a release OR tagging a version OR bumping VERSION OR publishing to GitHub releases.
base-toolsプラグインのバージョン（patchバージョン）をインクリメントし、commit-pushでコミット・プッシュする。「バージョンを上げて」「バージョンアップ」「bump version」などのリクエストで使用する。
Release a new version. Bumps minor version, creates git tag, pushes, and creates GitHub Release. Use when the user says "release" or wants to publish a new version.
Code quality linter definitions. Tells the Code Review Guardian agent which linters to check and run. Does NOT install anything. See PREREQUISITES.md for installation. --- # Code Review Guardian Tools ## Tool Inventory Check each linter's availability and detect project languages before scanning. Report status in the Tools Report. | Tool | Check Command | Purpose | Relevant When | |------|--------------|---------|---------------| | ESLint | `eslint --version` | Style, bugs, complexity | JavaScript/TypeScript (package.json) | | Ruff | `ruff --version` | Fast Python linter | Python projects | | Pylint | `pylint --version` | Deep Python analysis | Python projects | | Clippy | `cargo clippy --version` | Idiomatic Rust patterns | Rust projects (Cargo.toml) | | dotnet format | `dotnet format --version` | C# style and analyzers | C# projects (.csproj) | | Checkstyle | `mvn checkstyle:check` or `gradle checkstyleMain` | Java style and bugs | Java projects (pom.xml, build.gradle) | ## Scan Commands (run in parallel per language, when available) ``` # JavaScript/TypeScript eslint . --no-error-on-unmatched-pattern --format compact # Python ruff check . pylint --disable=C0114,C0115,C0116 --score=yes <files> # Rust cargo clippy --message-format=short # C# dotnet format --verify-no-changes --verbosity minimal # Java
Standardized process for committing changes and releasing a new version. Includes steps for bumping versions in package files, updating the CHANGELOG.md, ensuring the README.md is up to date, and creating git release tags. Use when the user asks to "prepare a release", "bump the version", or "release a new version".
