skills.rest
repairman29
repairman29COMMUNITY
Explore all skills by this author →
GitHub

keep-clis-sharp

Audit and update CLIs, npm dependencies, and repo scripts to current versions.

Updated Aug 23, 2026
Search Tags:#npm#dependencies#tooling#update#inventory#node#clis
One-click install
npx skills add https://github.com/repairman29/JARVIS --skill keep-clis-sharp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: keep-clis-sharp
Source: https://github.com/repairman29/JARVIS/tree/main/.cursor/skills/keep-clis-sharp
Command: npx skills add https://github.com/repairman29/JARVIS --skill keep-clis-sharp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and update CLI tools, npm packages, and repo scripts; ensure versions are current and documented. Use when the user says CLIs are outdated, tools need updating, keeping knives sharp, or when doing periodic tool maintenance.

Core Features & Use Cases

  • Inventory root package.jsons and platform CLIs, then check versions and identify outdated items.
  • Apply safe updates with minimal risk, documenting changes in jarvis/TOOLS.md and RUNBOOK.md.
  • Use cases include preparing for a release, maintenance sprint, or when platform/toolchain changes occur.

Quick Start

Inventory root and targeted package.json files, check versions, perform safe updates, and document changes.

Frequently Asked Questions about keep-clis-sharp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update outdated npm dependencies and CLI tools in my repository?▼

To update outdated npm dependencies and CLI tools, inventory root and targeted package.json files, check current versions, apply safe non-destructive upgrades, and document all version changes in TOOLS.md and RUNBOOK.md.

What is the safest way to inventory and refresh repository scripts before a release?▼

The safest way to inventory and refresh repository scripts is to audit root package.json files and platform CLIs, apply minimal-risk updates, and log the last sharpened date to ensure toolchain readiness before a release.

Can I apply non-destructive updates across multiple package.json files in a monorepo?▼

Yes, you can apply non-destructive updates across multiple package.json files by targeting root, apps/jarvis-ui, and olive-e2e configurations, refreshing versions safely unless explicitly approved for destructive changes.

How do I keep platform CLIs documented when upgrading to current versions?▼

To keep platform CLIs documented during upgrades, update TOOLS.md and RUNBOOK.md with new versions and usage changes whenever you apply upgrades, ensuring platform tooling documentation stays current and accurate.

When should I run a toolchain maintenance sprint to sharpen node CLIs and dependencies?▼

You should run a toolchain maintenance sprint to sharpen node CLIs and dependencies when preparing for a release, during periodic tool maintenance, or when platform and toolchain changes occur to ensure versions remain current.

Related Skills

Explore More Software Engineering Skills→
ashtonianashtonian
2

dependency-audit

Audit software dependencies across Go, Node.js, Python, Rust, and containers.

Community
Intermediate
sparkeh9sparkeh9
7

docling-upstream-upgrade

Automates the upstream Docling upgrade workflow with validation and baseline recording.

Community
Advanced
RzyfrontRzyfront
5

vendix-monorepo-workspaces

Manage npm monorepo dependencies and workspace configurations.

Community
Advanced
duc01226duc01226
7

package-upgrade

Analyze package.json files to plan staged dependency upgrades.

Community
Advanced