cli-update

Audit, update, test, and publish the clawcity npm CLI package.

4|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/marcel-heinz/clawcity.app --skill cli-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-update
Source: https://github.com/marcel-heinz/clawcity.app/tree/main/.claude/skills/cli-update
Command: npx skills add https://github.com/marcel-heinz/clawcity.app --skill cli-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit, update, test, and publish the clawcity npm CLI package to keep the tool aligned with API changes and new features.

Core Features & Use Cases

  • End-to-end CLI lifecycle management: audit the current package state on npm, scan the repository for CLI-affecting updates, analyze gaps between published and local code, update the CLI source, run local tests, and publish a new release.
  • Ensure compatibility with API changes and feature rollouts to maintain a stable command-line interface for developers.
  • Use Case: When API changes are deployed or a release is prepared, trigger this agent to refresh the CLI and release a new version.

Quick Start

Run the CLI update agent to audit the current package, apply updates, test locally, and publish a new release.

Frequently Asked Questions about cli-update

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

FAQPage Schema
How do I automate npm CLI package updates after API changes?

Automate npm CLI package updates by auditing the published package, scanning the repository for API changes, validating compatibility, updating source code, running tests, and publishing a new release. This keeps the CLI synchronized with backend changes.

What is the best way to audit and publish an npm CLI release?

The best way to audit and publish an npm CLI release is to run an end-to-end lifecycle management process that analyzes gaps between published and local code, applies source updates, runs local tests, and publishes the new version to npm.

When do I need to update my CLI package for API compatibility?

You need to update your CLI package for API compatibility when API changes are deployed or new features are rolled out. This ensures the command-line interface remains stable and functional for developers relying on it.

Can I run local tests before publishing my npm CLI package?

Yes, you can run local tests before publishing your npm CLI package. The update workflow includes a testing phase that executes local tests after applying source updates to validate compatibility and ensure the new release is stable.

Does the CLI update process scan the repository for code changes?

Yes, the CLI update process scans the repository for CLI-affecting updates. It analyzes gaps between the published npm package and local code to determine what source updates are needed before running tests and publishing.

What steps are involved in end-to-end CLI lifecycle management?

End-to-end CLI lifecycle management involves auditing the current package state on npm, scanning the repository for updates, analyzing compatibility gaps, updating CLI source code, running local tests, and publishing a new release to npm.