feat(skills-next): add nestjs SDK references

[evanpurkhiser]

Direct LLM port of the existing nestjs SDK skill into the skills-next per-SDK reference layout under skills-next/references/sdks/nestjs/. This content has NOT been reviewed at all — it is a machine-generated port of the existing SDK skill, and every file should be treated as unverified.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit bde6e02. Configure here.}

[cursor]

Missing await on isolation scope

Medium Severity

The cron example calls Sentry.withIsolationScope with an async callback but never awaits the returned promise, so the scheduled handler can finish before isolated work and Sentry context teardown complete. That undermines the documented goal of keeping job breadcrumbs and tags out of HTTP request scopes.

Additional Locations (1)

• skills-next/references/sdks/nestjs/index.md#L392-L399

 

^{Reviewed by Cursor Bugbot for commit bde6e02. Configure here.}

[sentry]

Bug: The documentation is contradictory, stating prismaIntegration is both manual and auto-enabled. This can lead to developers incorrectly assuming it's automatic and missing tracing data.
_{Severity: MEDIUM}

Suggested Fix

To resolve the contradiction, remove prismaIntegration from the list of auto-enabled database integrations at line 669. The documentation should consistently state that it requires manual configuration.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: skills-next/references/sdks/nestjs/tracing.md#L553

Potential issue: The documentation for the NestJS SDK contains conflicting information
regarding the Sentry Prisma integration. One section states that `prismaIntegration`
requires manual setup (`⚠️ Manual`), while another section incorrectly lists it under
"Databases (all auto-enabled)". A developer following the latter section would assume
Prisma tracing is enabled by default, leading to a silent failure where no
Prisma-related spans are captured. This results in missing observability data in
production without any warning or error.

Also affects:

• skills-next/references/sdks/nestjs/tracing.md:669~669

_{Did we get this right? 👍 / 👎 to inform future reviews.}