testing-prpm-cli

Test PRPM CLI commands against a local registry for conversions and contracts.

121|16|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/pr-pm/prpm --skill testing-prpm-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-prpm-cli
Source: https://github.com/pr-pm/prpm/tree/main/.claude/skills/testing-prpm-cli
Command: npx skills add https://github.com/pr-pm/prpm --skill testing-prpm-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, node.

What problem does it solve?

This Skill eliminates guesswork when testing PRPM CLI commands by providing comprehensive workflows for local development, cross-format conversion testing, and critical contract validation.

Core Features & Use Cases

  • Local Development Testing: Build, configure, and test CLI commands against a local registry.
  • Cross-Format Conversion: Test conversions across all 15+ supported formats including Claude, Cursor, Windsurf, and Gemini.
  • Contract Testing: Verify documented behavior matches implementation across all precedence paths and default cases.
  • Use Case: When developing a new CLI feature, use this Skill to test all documented behaviors, verify format conversions work correctly, and ensure no regression in existing functionality.

Quick Start

Build the CLI and test a search command: npm run build --workspace=packages/cli && export PRPM_REGISTRY_URL=http://127.0.0.1:3111 && node packages/cli/dist/index.js search typescript

Frequently Asked Questions about testing-prpm-cli

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

FAQPage Schema
How do I test CLI commands against a local registry during development?

Test PRPM CLI commands by building the package, starting a local registry, configuring the registry URL via PRPM_REGISTRY_URL environment variable, and invoking CLI commands directly. This workflow verifies built packages, environment setup, and documented behavior in isolation before deployment.

Can I test format conversions across multiple supported formats with a single workflow?

Yes, this Skill tests conversions across 15+ supported formats including Claude, Cursor, Windsurf, and Gemini formats. It orchestrates build, registry configuration, and comprehensive conversion testing to verify all format outputs work correctly.

What is contract testing and why does it matter for CLI validation?

Contract testing verifies that documented CLI behavior matches the actual implementation across all precedence paths and default cases. It ensures no regression in existing functionality and catches discrepancies between specification and code.

Do I need Node.js and npm to run these CLI tests?

Yes, Node.js and npm are required dependencies. The Skill uses npm for building the CLI workspace and node to invoke the compiled CLI commands against the local registry.

How do I validate a new CLI feature without breaking existing functionality?

Build the CLI, configure a local registry environment, run contract tests across all documented behaviors and format conversions, then verify the new feature integrates without regression. This comprehensive testing catches issues before deployment.