skills.rest
en-dash-consulting
en-dash-consultingOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dev-link

Switches ndx between local development build and published npm version.

16|9|Updated Mar 5, 2026
Search Tags:#npm#development-workflow#local-dev#global-install#ndx#build-switch#binary-resolution
One-click install
npx skills add https://github.com/en-dash-consulting/n-dx --skill dev-link
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-link
Source: https://github.com/en-dash-consulting/n-dx/tree/main/.claude/skills/dev-link
Command: npx skills add https://github.com/en-dash-consulting/n-dx --skill dev-link

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swapping between a local development build and the published npm version can be error-prone and time-consuming. This Skill streamlines that workflow, reducing friction for developers.

Core Features & Use Cases

  • Easy toggling between local dev and npm-distributed builds.
  • Verifies active version and resolves binaries for correct ndx/command behavior.
  • Use Case: A developer wants to verify that the global ndx points to their local build before integrating changes.

Quick Start

Run /dev-link with no arguments to view the current state, or use /dev-link local to switch to the local dev build, or /dev-link npm to switch back to the npm version.

Frequently Asked Questions about dev-link

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

FAQPage Schema
How do I switch between a local development build and the npm version?▼

Switching between a local development build and the npm version requires toggling the active source directory. This process encodes commands for linking, unlinking, and inspecting the current source to ensure correct binary resolution.

What is the best way to verify that my global npm binary points to my local dev build?▼

Verifying that your global binary points to your local dev build involves inspecting the current source state. Running a status command with no arguments displays the active version and confirms correct binary resolution before integrating changes.

Does this local dev linking workflow require any specific dependencies?▼

This local dev linking workflow does not require any specific dependencies. It operates independently to manage binary resolution and build switching, allowing developers to quickly toggle between local and npm-distributed releases without additional setup.

Why does binary resolution fail when swapping between local dev and npm releases?▼

Binary resolution fails when swapping between local dev and npm releases due to incorrect active source toggling. An error-prone manual linking process can be fixed by using a dedicated command to properly unlink the local build and switch back to the npm version.

Can I inspect the current ndx source state without modifying the active build?▼

Inspecting the current ndx source state without modifying the active build is possible by running the command with no arguments. This displays the current state, verifying the active version and ensuring correct command behavior without toggling.

Related Skills

Explore More Software Engineering Skills→
ValyntValynt

setup-dev-environment

Clone the repository and configure a local ValueOS development environment.

Official
Advanced
kjfsmkjfsm
1

release

Enforce pre-release checks before publishing npm packages via changesets.

Community
Intermediate
ray-manalotoray-manaloto
1

mise-lang-node-packages

Pin Node package managers with corepack and mise for consistent tooling.

Official
Intermediate
different-aidifferent-ai
249

publish-cli

Publish the agent-bank CLI to npm and verify its version.

Official
Intermediate