# How to Update k-skill to the Latest Version: Complete Update Guide

> Update k-skill to the latest version with this complete guide. Learn how to reinstall the global CLI or pull the latest commit directly from GitHub.

- Repository: [NomaDamas/k-skill](https://github.com/NomaDamas/k-skill)
- Tags: how-to-guide
- Published: 2026-08-04

---

**Run `npm install -g @nomadamas/k-skill@0` to reinstall the global CLI for the newest 0.x release, or use `npx --yes skills add NomaDamas/k-skill --all -g` to pull the latest commit directly from GitHub.**

The **k-skill** project from [NomaDamas](https://github.com/NomaDamas/k-skill) is an npm-workspace monorepo that provides a CLI tool for managing AI-powered skills. The public CLI package `@nomadamas/k-skill` publishes to npm automatically whenever a Changeset merges, which means updating the CLI automatically brings all workspace packages up to date. This guide covers every method to update k-skill while preserving your configuration.

## Update Methods for k-skill

The repository supports two primary distribution channels: the npm registry for stable releases and direct GitHub cloning for bleeding-edge updates. Choose the method that matches your installation style.

### Global CLI Reinstallation (npm Registry)

The most straightforward way to update k-skill is reinstalling the global CLI package. The `@0` tag always resolves to the latest `0.x` release according to the [installation documentation](https://github.com/NomaDamas/k-skill/blob/main/docs/install.md).

```bash
npm install -g @nomadamas/k-skill@0

```

This command replaces your existing binary with the current release. Run it again whenever you want to refresh to the newest published version.

### One-Off Execution Without Global Install (npx)

If you prefer not to maintain a global installation, use **npx** to run the latest CLI on demand:

```bash
npx -y @nomadamas/k-skill@0 list

```

Swap `list` with any k-skill command (`instruct`, `exec`, `search`, etc.). The `-y` flag skips the installation prompt and executes immediately.

### Skill-Tool Full Reinstall (GitHub Source)

For a **git-like** workflow that bypasses npm entirely, the `skills` command fetches directly from the repository. This pulls the newest commit and regenerates all skill packages as documented in the [main README](https://github.com/NomaDamas/k-skill/blob/main/README.md#설치):

```bash
npx --yes skills add NomaDamas/k-skill --all -g

```

The `--all` flag ensures every workspace package in `packages/*` refreshes to match the latest source.

### Partial Skill Update (Specific Package Only)

To update individual skills without touching others, specify the skill name:

```bash
npx --yes skills add NomaDamas/k-skill --skill <skill-name> -g

```

Replace `<skill-name>` with the target package from the `packages/` directory. This preserves your existing installations of untouched skills.

## Verify Your k-skill Version

After updating, confirm the installation succeeded:

```bash
k-skill --version                  # Displays installed CLI version

npm list -g @nomadamas/k-skill     # Shows exact npm package version

```

Version mismatches between these outputs typically indicate a cached npx execution or multiple global installations.

## Post-Update Configuration Check

If you use the **k-skill-setup** skill for credential management, rerun it after updating:

```bash
k-skill setup

```

New releases occasionally introduce additional environment-variable requirements. The setup skill detects these and prompts for missing values.

## How k-skill Release Automation Works

Understanding the release pipeline helps you choose the right update timing. The repository uses **Changesets** to version and publish automatically:

- **Release trigger**: Merging a Changeset in `.changeset/` runs [`.github/workflows/release-npm.yml`](https://github.com/NomaDamas/k-skill/blob/main/.github/workflows/release-npm.yml)
- **Package publication**: The workflow publishes `@nomadamas/k-skill` and all `packages/*` workspace members
- **CLI behavior**: The thin CLI wrapper in `packages/k-skill-cli/` resolves and loads the appropriate skill bundle at runtime

Detailed release procedures live in [[`docs/releasing.md`](https://github.com/NomaDamas/k-skill/blob/main/docs/releasing.md)](https://github.com/NomaDamas/k-skill/blob/main/docs/releasing.md). The npm publish triggered by this workflow is what your update commands consume.

## Key Files for Update Troubleshooting

| File Path | Purpose |
|-----------|---------|
| [`docs/install.md`](https://github.com/NomaDamas/k-skill/blob/main/docs/install.md) | Official installation and update commands |
| [`docs/releasing.md`](https://github.com/NomaDamas/k-skill/blob/main/docs/releasing.md) | Changeset-based release automation details |
| `packages/k-skill-cli/` | CLI source that loads skill bundles |
| [`.github/workflows/release-npm.yml`](https://github.com/NomaDamas/k-skill/blob/main/.github/workflows/release-npm.yml) | Workflow that publishes versions you update to |
| `packages/*` | Workspace packages automatically refreshed on update |

## Summary

- **Global npm reinstall**: `npm install -g @nomadamas/k-skill@0` for stable registry releases
- **npx on-demand**: `npx -y @nomadamas/k-skill@0 <command>` for temporary execution
- **GitHub full refresh**: `npx --yes skills add NomaDamas/k-skill --all -g` for latest commits
- **Selective update**: Add `--skill <name>` to update specific packages only
- **Always verify**: Run `k-skill --version` and re-execute `k-skill setup` post-update

## Frequently Asked Questions

### Will updating k-skill erase my skill configurations?

No. Skill configurations and credentials persist outside the installation directory. The **k-skill-setup** skill stores environment variables in your shell profile or designated config files. Running `k-skill setup` after update only checks for new required variables—it does not overwrite existing valid configurations.

### Why does `@nomadamas/k-skill@0` install a different version than the GitHub repository?

The npm registry lags behind GitHub commits by the duration of the release pipeline. The `@0` tag points to the latest **published** 0.x release, while `skills add --all` clones the **current** default branch. Use npm for stability; use `skills` for immediate access to unreleased changes.

### How do I downgrade k-skill if an update breaks my workflow?

Specify an exact version instead of the `@0` tag:

```bash
npm install -g @nomadamas/k-skill@0.4.2

```

Find historical versions with `npm view @nomadamas/k-skill versions --json`. For GitHub-based installs, append a commit SHA or tag to the repository URL in your `skills` command.

### Can I automate k-skill updates in CI/CD pipelines?

Yes. Use `npm install -g @nomadamas/k-skill@0` or `npx -y @nomadamas/k-skill@0` in your workflow. Pin to a specific version for reproducible builds, or use `@0` to always test against the latest release. The `skills` tool requires network access to GitHub and longer clone times, making npm preferable for most CI environments.