Add `pnpm nx` command patterns for Nx monorepos

[mkbctrl]

Problem

pnpm nx * commands are not covered by RTK's rewrite/compression patterns, causing them to pass through uncompressed. In our monorepo (Nx-managed, 20+ projects), we observed 313 pnpm nx * passthrough invocations in a single audit window — making this the largest single category of uncompressed output.

Related Issues

• Support for pnpm and glab cli #122 — pnpm + glab integration (P3)
• pnpm --filter command results in rtk usage output #259 — pnpm --filter support (PR feat(pnpm): Add filter argument support #270 open)
• Hook rewrite: add coverage for uv run, pnpm exec, Python path variants, and more #294 — pnpm exec / script dispatch

These all point to the same gap: pnpm as a command prefix is not systematically handled.

High-Impact Patterns

Command	Frequency	Notes
pnpm nx run <project>:<target>	~180	Build, typecheck, lint, test
pnpm nx show project <name>	~60	Project details (large JSON output)
pnpm nx graph	~30	Dependency graph
pnpm nx affected	~25	CI/change detection
pnpm nx run-many	~18	Batch operations

Suggested Approach

Add pnpm nx as a recognized command prefix in the rewrite rules, delegating to existing patterns where the underlying command is already supported (e.g., pnpm nx run -> build output compression).

Environment

• RTK v0.27.2
• pnpm v9.x
• Nx 20.x monorepo

[pszymkowiak]

wshm · Automated triage by AI

🔍 Automated Triage

✨ Category	feature
🟡 Priority	medium
🎯 Confidence	93%

Summary

Add rewrite/compression patterns for pnpm nx command prefix in Nx monorepos; well-scoped enhancement with clear frequency data and existing related issues.

---

Triaged automatically by wshm · This is an automated analysis, not a human review.