CLI Help Examples
Copy-paste ready examples for common pair-cli workflows with expected output.
Copy-paste ready examples for common pair-cli workflows. All examples include expected output as comments.
Installation Workflows
1. First-time Setup
Output:
2. Install to Custom Directory
3. Install Specific Registries Only
4. Install from Custom KB Source (Remote)
5. Install from Local KB Source
6. Offline Installation (Air-Gapped Environment)
Update Workflows
7. Update Existing Installation
8. Update Specific Registry
9. Update from Custom Source
Validation Workflows
10. Validate KB Structure and Links
11. Validate with Zero Tolerance
Every missing internal target is an error and any declared optional link patterns are
discarded. It checks no external links: the CLI makes no network requests, so
http/https links are never fetched, with or without --strict.
12. Validate Source Layout
13. Validate Excluding Registries
14. Validate Without Config
No config is consulted, so no registry resolves, no file is collected and nothing is
validated, structure, links and metadata are all skipped, and the run says so with a
Configuration: notice. Use it to skip validation, not to run with CLI-only patterns.
15. Validate Default Configuration
16. Validate Custom Configuration
Link Management Workflows
17. Validate and Fix Links
18. Preview Link Updates (Dry Run)
19. Update Links with Verbose Output
Packaging Workflows
20. Package KB for Distribution
21. Package with Custom Output Path
22. Package with Metadata
23. Package Specific Source Directory
24. Package Excluding Registries
25. Interactive Package Creation
26. Organizational Package
Package Info and Verification
27. Display Package Metadata
28. Verify Package Integrity
29. Verify with JSON Output
30. Verify Before Installation
Advanced Workflows
31. Complete CI/CD Pipeline
32. Air-Gapped Environment Workflow
33. Multi-Environment Setup
Monorepo usage
When pair-cli is a dependency of a package inside a monorepo, run it with pnpm --filter from the root; the CLI reads INIT_CWD so the output lands at the monorepo root, not in the filtered package:
Setup scripts and CI
Maintenance after an update
Try it in a temporary directory
Related
- CLI commands: complete command documentation
- Install sources: every
--sourceform - update-link: link validation and repair
- KB source resolution: the resolution algorithm