taze

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

The skill is based on
taze
(latest README on GitHub) as of 2026-02-24.

taze

is a lightweight CLI for upgrading dependencies in JavaScript/TypeScript projects and monorepos. It focuses on safe-by-default version bumps, powerful filtering, and configuration via flags or

taze.config.(js|ts)

so agents can orchestrate dependency maintenance workflows.

This skill is written for agents that:

Need to review or perform dependency upgrades using
```
taze
```
Work in monorepos and must keep workspace packages in sync
Must follow safety policies around tests, lint/typecheck, and upgrade strategy

本Skill基于截至2026年2月24日GitHub上最新README的
taze
开发。

taze

是一款轻量级CLI工具，用于升级JavaScript/TypeScript项目及Monorepo中的依赖。它默认以安全为核心进行版本更新，具备强大的过滤功能，并支持通过命令行参数或

taze.config.(js|ts)

配置文件进行设置，方便Agent编排依赖维护工作流。

本Skill适用于以下场景的Agent：

需要使用
```
taze
```
查看或执行依赖升级操作
工作在Monorepo环境中，需要保持工作区包版本同步
必须遵循包含测试、代码检查/类型校验及升级策略在内的安全规范

Core References

核心参考资料

Topic	Description	Reference
Overview & CLI modes	`taze` goals, install-free usage, major/minor/patch modes	core-overview
Monorepo support	`-r` recursive mode, workspaces, local packages	core-monorepo

主题	描述	参考链接
概述与CLI模式	`taze` 的目标、免安装使用方式、大版本/小版本/补丁版本更新模式	core-overview
Monorepo支持	`-r` 递归模式、工作区、本地包	core-monorepo

Features

功能特性

Configuration & Filtering

配置与过滤

Topic	Description	Reference
Config file usage	`taze.config.js/ts` , `defineConfig` , options mapping	features-config-file
Filters & peer deps	`--include/--exclude` , locked deps, `--peer` , dep fields	features-filters-and-peer-deps

主题	描述	参考链接
配置文件使用	`taze.config.js/ts` 、 `defineConfig` 、选项映射	features-config-file
过滤与Peer依赖	`--include/--exclude` 、锁定依赖、 `--peer` 、依赖字段	features-filters-and-peer-deps

Best Practices & Upgrade Policy

最佳实践与升级策略

Topic	Description	Reference
Safe upgrade workflow	When to upgrade, required checks (tests, e2e, lint, typecheck), major-default policy with fallback	best-practices-upgrade-strategy

主题	描述	参考链接
安全升级工作流	升级时机、必要检查（测试、端到端测试、代码检查、类型校验）、默认大版本更新策略及回退方案	best-practices-upgrade-strategy