How do I install the Audit Better Result Dependents skill?

Run npx skillmds@latest add dmmulroy-better-result/audit-better-result-dependents in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Audit Better Result Dependents safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Audit Better Result Dependents?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Audit Better Result Dependents free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Audit Better Result Dependents?

dmmulroy (@dmmulroy-better-result) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Audit Better Result Dependents by dmmulroy-better-result

Name: Audit Better Result Dependents
Rating: 4.5 (4 reviews)
Author: dmmulroy

Audit Better Result Dependents

Audit better-result changes or PRs against known Prisma and Better T Stack downstream dependents. Use when working on better-result API/type/runtime changes and the user asks whether a change breaks Prisma dependents, Better T Stack dependents, npm dependents, or PR compatibility.

dmmulroy Updated Sep 9, 2026

File contents

Audit better-result dependents

Quick start

From the better-result repo, run the audit script with identifiers touched by the change:

node .agents/skills/audit-better-result-dependents/scripts/audit-dependents.mjs isTaggedError 'TaggedError\.is' 'toJSON'

If no patterns are provided, the script searches common better-result usage patterns.

Scope

Always check these npm dependents:

@prisma/compute-sdk
@prisma/streams-server
@prisma/streams-local
create-better-t-stack
@better-t-stack/template-generator

The script uses npm registry metadata to resolve latest versions and commits. For public GitHub repos it checks out the published gitHead; if a repo is private/unavailable, it falls back to npm pack and audits the published source/package.

Workflow

Identify risk surface
- List changed public exports, guards, types, class methods, overloads, and runtime semantics.
- Convert them into grep patterns, escaping regex metacharacters when needed.
Run local validation first
- bun run fmt
- bun run check
- bun run test
- bun run lint
Audit dependents
- Run the script with risk patterns.
- Inspect actual matching files with read; do not rely only on counts.
- Distinguish generic guards (e.g. isTaggedError) from class-specific guards (e.g. FooError.is).
Assess breakage
- Runtime breaking: dependent passes values that no longer satisfy a changed guard/shape.
- Type breaking: dependent references narrowed types, overloads, exported names, or structural constraints that changed.
- Safe: dependent only creates TaggedError(...) instances or uses class-specific .is() unaffected by the change.
Report clearly
- Include package name, version, source audited (GitHub commit or npm package), relevant matches, and risk conclusion.
- If opening a PR, include the dependent audit summary in the PR body.

Notes

@prisma/compute-sdk may point at a private/404 GitHub repo; audit the npm package source when cloning fails.
@prisma/streams-server and @prisma/streams-local share the prisma/streams repo and usually the same gitHead.
create-better-t-stack and @better-t-stack/template-generator share the AmanVarshney01/create-better-t-stack repo and usually the same gitHead.
Never modify cloned dependent repositories during audit; use temp directories only.

---name: audit-better-result-dependentsdescription: Audit better-result changes or PRs against known Prisma and Better T Stack downstream dependents. Use when working on better-result API/type/runtime changes and the user asks whether a change breaks Prisma dependents, Better T Stack dependents, npm dependents, or PR compatibility.--- # Audit better-result dependents ## Quick start From the `better-result` repo, run the audit script with identifiers touched by the change: ```sh node .agents/skills/audit-better-result-dependents/scripts/audit-dependents.mjs isTaggedError 'TaggedError\.is' 'toJSON' ``` If no patterns are provided, the script searches common `better-result` usage patterns. ## Scope Always check these npm dependents: - `@prisma/compute-sdk` - `@prisma/streams-server` - `@prisma/streams-local` - `create-better-t-stack` - `@better-t-stack/template-generator` The script uses npm registry metadata to resolve latest versions and commits. For public GitHub repos it checks out the published `gitHead`; if a repo is private/unavailable, it falls back to `npm pack` and audits the published source/package. ## Workflow 1. **Identify risk surface** - List changed public exports, guards, types, class methods, overloads, and runtime semantics. - Convert them into grep patterns, escaping regex metacharacters when needed. 2. **Run local validation first** - `bun run fmt` - `bun run check` - `bun run test` - `bun run lint` 3. **Audit dependents** - Run the script with risk patterns. - Inspect actual matching files with `read`; do not rely only on counts. - Distinguish generic guards (e.g. `isTaggedError`) from class-specific guards (e.g. `FooError.is`). 4. **Assess breakage** - Runtime breaking: dependent passes values that no longer satisfy a changed guard/shape. - Type breaking: dependent references narrowed types, overloads, exported names, or structural constraints that changed. - Safe: dependent only creates `TaggedError(...)` instances or uses class-specific `.is()` unaffected by the change. 5. **Report clearly** - Include package name, version, source audited (GitHub commit or npm package), relevant matches, and risk conclusion. - If opening a PR, include the dependent audit summary in the PR body. ## Notes - `@prisma/compute-sdk` may point at a private/404 GitHub repo; audit the npm package source when cloning fails. - `@prisma/streams-server` and `@prisma/streams-local` share the `prisma/streams` repo and usually the same `gitHead`. - `create-better-t-stack` and `@better-t-stack/template-generator` share the `AmanVarshney01/create-better-t-stack` repo and usually the same `gitHead`. - Never modify cloned dependent repositories during audit; use temp directories only.

Frequently asked questions