update

Check for and apply PM-Kit framework updates from GitHub releases.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ThuHuynh1438/pm-kit --skill update-thuhuynh1438
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/ThuHuynh1438/pm-kit/tree/main/.claude/skills/update
Command: npx skills add https://github.com/ThuHuynh1438/pm-kit --skill update-thuhuynh1438

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Check for and apply PM-Kit framework updates from GitHub releases, ensuring your tools stay current.

Core Features & Use Cases

  • Reads the local VERSION file to determine current framework version, queries GitHub for the latest release, and presents a changelog.
  • Backups and safely updates framework files without touching user content, with support for --check and --dry-run modes.
  • Useful for maintaining production-ready tooling in developer workflows and ensuring compatibility with templates, skills, and docs.

Quick Start

Run the /update command to check for the latest PM-Kit framework release and apply updates.

Frequently Asked Questions about update

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

FAQPage Schema
How do I update the PM-Kit framework to the latest GitHub release?

Updating the PM-Kit framework via the /update command checks the local VERSION file, queries the GitHub API for the latest release, then performs a backup and overwrite process without touching user content.

Can I check for PM-Kit updates without applying them?

Yes, you can check for PM-Kit updates without modifying files by using the --check or --dry-run modes, which report version differences and present the changelog without applying the actual update.

What does the PM-Kit update process do to protect user content?

The PM-Kit update process protects user content by backing up existing framework files before downloading and overwriting them, ensuring user content like templates and docs remains completely untouched during the update.

Why do I need to run /push after applying a PM-Kit framework update?

You need to run /push after a PM-Kit framework update because the automated download and overwrite process modifies local framework files, requiring you to manually commit the new version changes to your repository.

Does the PM-Kit update tool work without manual version tracking?

No, the PM-Kit update tool relies on reading the local VERSION file to determine your current framework version, then queries the GitHub API to compare it against the latest available release.