Updates npm, Rust, and Python dependencies to latest versions and refactors code broken by major releases.
npx skills add https://github.com/nitra/7n-test --skill n-taze-nitra
Please help me install this Agent Skill. Skill: n-taze Source: https://github.com/nitra/7n-test/tree/main/.cursor/skills/n-taze Command: npx skills add https://github.com/nitra/7n-test --skill n-taze-nitra
taze, Rust crates via cargo upgrade --incompatible allow, and Python packages via uv remove/uv add --bounds lower, all orchestrated deterministically per package. - Major-change analysis: Classifies semver-major jumps with caret semantics, collects breaking changes from CHANGELOGs or cached-version diffs, and searches your codebase for affected usages with ripgrep. - Automated refactoring with verification: Migrates incompatible call sites, then runs lint, typecheck, and tests (or cargo clippy/test, ruff/mypy/pytest) and produces a structured report of updated, refactored, and manually-actionable items. - Use Case: Run it in a monorepo before a release to lift every dependency to latest, get a per-package report of major upgrades, and have simple breaking changes (renamed exports, changed signatures) fixed automatically with tests re-run. ## Quick Start Ask the agent to update all project dependencies to their latest versions, analyze major breaking changes, and refactor any incompatible code, then report what needs manual attention.High-intent search queries and answers about installing and using this skill.
Run bunx taze -w -r latest followed by bun install to rewrite package.json versions across all workspaces, then use n-rules taze diff to get a JSON list of major bumps. The skill then checks each major package's changelog and refactors affected code.
Use cargo upgrade --incompatible allow from cargo-edit, then cargo update to sync Cargo.lock. Without cargo-edit, plain cargo update only applies semver-compatible bumps, so major upgrades cannot be applied deterministically.
uv has no single command to bump everything past major boundaries; uv add on an existing dependency is a no-op. The deterministic approach is uv remove <pkg> followed by uv add <pkg> --bounds lower for each direct dependency.
Yes, missing tools do not block other ecosystems. The orchestrator skips the Rust or Python branch and lists the found Cargo.toml or pyproject.toml files in the report as requiring a manual run.
It is a worktree-only skill that creates .worktrees/<branch>-taze/ so dependency upgrades and refactoring never touch your main working tree. Only one instance runs at a time, and a preflight check stops execution if the worktree setup fails.
The skill does not guess on nontrivial migrations. It leaves a TODO in the code linking to the changelog and lists the item in the final report under manual actions, along with lint, typecheck, and test pass/fail status.
supermalangAudit project dependencies for vulnerabilities, outdated packages, and risky licenses.
coferlandiaCoordinates skill versions, changelogs, release notes, and plugin packaging through one deterministic release gate.
adityaarsharmaManage regression test suites with Playwright and CI pipelines.
AisleiAvilaAutomate major npm or yarn dependency upgrades with validation and rollback planning.