pry

name

pry

description

Use when reviewing the testability/injectability of TypeScript/JavaScript code, or when `quality` wants pry's testability backlog. Runs the pry static analyzer (honoring PRY_BIN), ranks the welded-at-demand findings (boundary calls with no seam to inject a failure), and labels each GENUINE / FALSE-WELD / COSMETIC / AMBIGUOUS. Emits a risk ranking, not a bug list. TS/JS only — Python is a recorded KILL.

pry (F15 intelligence skill)

pry the binary is deterministic and dumb (spec F1): pry map <path> emits every boundary finding classified seamed / welded / ambiguous, with the substitution-demand flag and the cosmetic-clock + duration-record + cosmetic-random filters (plus the clock control-vs-record discrimination rescue, which keeps DB-query date bounds and compared date-math thresholds in the demand subset) already applied. This skill is the intelligence layer the CLI defers to: it runs the binary, ranks the welded-at-demand backlog, and labels each finding. The output is advisory — a testability backlog, never a bug list, and it must never fail standing quality.

When to use

• A user asks "is this TS/JS testable?", "where are the un-injectable boundaries?", or wants the welded-at-demand / injectability backlog.
• quality wants pry's advisory testability inventory for a TS/JS path.

Not for Python: the author's Python is welded glue with no discrimination — a recorded KILL (docs/kill-gate.md). pry analyzes .ts/.tsx/.js/.mjs/.cjs only.

Prerequisite: the binary

pry v0.1.0 is published. Resolve the binary in this order (the consumer does this for you):

1. PRY_BIN=/abs/path/to/pry/target/release/pry (maintainer-local override — prefer when testing a sibling checkout).
2. pry on PATH.
3. install the published release (prebuilt binary): curl --proto '=https' --tlsv1.2 -LsSf https://github.com/corca-ai/pry/releases/latest/download/pry-installer.sh | sh
4. a target/release/pry build inside the pry checkout (cargo build --release).

Workflow: run → rank → label

1. Run + rank (the prescribed command — reproduce exactly):

PRY_BIN=/abs/path/to/pry/target/release/pry \
  python3 skills/pry/scripts/rank_backlog.py <ts-or-js-path> [--top N] [--json]

This projects the welded-at-demand backlog = findings where demand=true and class="welded", sorted high-precision-kind first (subprocess → llm → db → network → slack → clock → random; order from the docs/precision-gate.md census) then by file:line. It is deterministic (byte-identical across runs). fileio/env are the diagnostic swamp and are excluded from the demand subset by design.

2. Label each backlog finding by reading its file:line (the binary cannot — this is the skill's job). Use the docs/precision-gate.md taxonomy:

• GENUINE — real weld, on/near a failure path, no seam to inject a failure, worth making injectable. (This is the actionable backlog.)
• FALSE-WELD — actually already seamed via an injected interface/factory/param pry's leaf model missed (a rung-3 gap). Report as a pry recall gap, not a code gap.
• COSMETIC — real weld but outside the thesis: a display/record value (new Date().toISOString() as a field, temp-name randomness) with no failure to inject.
• AMBIGUOUS — local context can't decide control-vs-record use.

3. Report the GENUINE findings as the testability backlog (file:line, kind, why no seam, suggested injection seam). State precision honestly: cite how many were GENUINE vs noise. Advisory only.

Self-test

The prescribed command above, run against any TS path with boundaries, is the skill's self-test: it must emit a deterministic WELDED-AT-DEMAND BACKLOG ranking. Validated against ../ceal/packages (67 welded-at-demand findings, matches the frozen fixtures/ceal-ts-map.summary.json).

Degraded behavior

No binary — or a path that scans nothing — → the consumer returns status: degraded with a hint and exit 1. Treat the testability backlog as simply unavailable; pry is advisory and standalone, so nothing else is affected. Do not claim a testability review succeeded without a healthy binary.

References

• docs/precision-gate.md — the labeling taxonomy + per-kind precision census.
• docs/kill-gate.md — why TS/JS only (Python KILL).
• skills/pry/scripts/rank_backlog.py — the PRY_BIN-honoring consumer.
• ../charness/integrations/tools/pry.json — the charness external_binary manifest.