# Taze

> Keep JavaScript/TypeScript dependencies fresh with safety rails and monorepo support.

- Skill: `hairyf-skills/taze` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add hairyf-skills/taze`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hairyf-skills/taze/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: hairyf (https://skillmd.com/u/hairyf-skills)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/hairyf-skills/taze

---


> 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

## Core References

| Topic | Description | Reference |
|-------|-------------|-----------|
| Overview & CLI modes | `taze` goals, install-free usage, major/minor/patch modes | [core-overview](references/core-overview.md) |
| Monorepo support | `-r` recursive mode, workspaces, local packages | [core-monorepo](references/core-monorepo.md) |

## Features

### Configuration & Filtering

| Topic | Description | Reference |
|-------|-------------|-----------|
| Config file usage | `taze.config.js/ts`, `defineConfig`, options mapping | [features-config-file](references/features-config-file.md) |
| Filters & peer deps | `--include/--exclude`, locked deps, `--peer`, dep fields | [features-filters-and-peer-deps](references/features-filters-and-peer-deps.md) |

## 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](references/best-practices-upgrade-strategy.md) |


