swpm-manage-commands-args

Synchronize cmds and args mappings across SWPM package-manager configs.

125|5|Updated May 13, 2022
One-click install
npx skills add https://github.com/deinsoftware/swpm --skill swpm-manage-commands-args
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swpm-manage-commands-args
Source: https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-manage-commands-args
Command: npx skills add https://github.com/deinsoftware/swpm --skill swpm-manage-commands-args

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and synchronize the Cmds and Args mappings across SWPM's package manager configs (src/packages/managers/*.ts) to ensure consistent behavior across npm, yarn, pnpm, bun, and deno. This streamlines updates and reduces drift when commands or their arguments differ between package managers.

Core Features & Use Cases

  • Centralized mapping edits: modify cmds/args in one place and propagate to all manager files.
  • Template-guided changes: follow the templates in templates/commands.md and templates/args.md to ensure consistent shapes and behaviors.
  • Real-world scenarios: adding a new command mapping, adjusting an existing one, or removing unsupported mappings across all managers.

Quick Start

Edit the target files under src/packages/managers/*.ts to adjust cmds and args mappings, then run npm run build and npm run test to verify.

Frequently Asked Questions about swpm-manage-commands-args

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

FAQPage Schema
How do I synchronize command mappings across multiple JavaScript package managers?

To synchronize command mappings, edit the cmds and args configurations within TypeScript manager files to ensure consistent behavior across npm, yarn, pnpm, bun, and deno. This standardizes updates and reduces configuration drift when commands differ between managers.

What is the best way to add a new package manager command mapping without breaking existing configurations?

To add a package manager command mapping safely, follow template guidelines to ensure consistent shapes and behaviors. Update the correct manager files and templates, verify changes propagate consistently across all managers, then run build and test steps.

How do package manager argument mappings work when commands differ across npm, yarn, and pnpm?

Argument mappings work by applying template-guided changes that standardize how arguments are passed across different package manager configurations. This ensures mapped arguments produce consistent execution behavior across npm, yarn, pnpm, bun, and deno.

Can I use template files to standardize command and argument shapes for TypeScript package manager configs?

Yes, template files standardize command and argument shapes for TypeScript package manager configs. Template-guided changes ensure consistent shapes and behaviors across all manager files, streamlining updates and reducing drift when commands or arguments differ.

What are the limitations of centralized command mapping edits for multiple package managers?

Centralized command mapping edits require updating correct manager files and templates to ensure consistency. Limitations include the necessity of running build and test verification steps after modifying mappings, as failing to verify changes can lead to undetected drift across package manager configurations.