record-gotchas

Capture developer friction with Prisma products and create Linear triage tickets.

47.5k|2.5k|Updated Jun 20, 2019
One-click install
npx skills add https://github.com/prisma/prisma --skill record-gotchas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-gotchas
Source: https://github.com/prisma/prisma/tree/main/skills-contrib/record-gotcha
Command: npx skills add https://github.com/prisma/prisma --skill record-gotchas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires plugin-linear-linear.

What problem does it solve?

This skill captures the friction, surprises, and undocumented behaviors encountered while consuming Prisma products, ensuring that valuable developer insights are not lost and are properly triaged for the product team.

Core Features & Use Cases

  • Standardized Capture: Provides a consistent template for recording gotchas, including symptoms, causes, and workarounds.
  • Linear Integration: Automatically files Triage-state tickets in the appropriate Linear project to ensure team visibility.
  • Use Case: When you encounter a confusing CLI error or an undocumented behavior while building an extension, use this skill to document the issue and create a tracking ticket in one seamless workflow.

Quick Start

Use the record-gotchas skill to document the unexpected behavior I just encountered with the Prisma Next CLI and file a ticket in the appropriate project.

Frequently Asked Questions about record-gotchas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document undocumented Prisma CLI errors and track them automatically?

To document undocumented Prisma CLI errors and track them, use a standardized capture template for symptoms, causes, and workarounds, then automatically file Triage-state tickets in the appropriate Linear project to ensure team visibility and triaging.

What is the best way to capture developer friction when using Prisma Postgres?

The best way to capture developer friction when using Prisma Postgres is to formalize the encountered surprises and undocumented behaviors into a consistent gotcha record, integrating local documentation updates with upstream Linear ticket creation for product team tracking.

Do I need a Linear plugin to file bug tracking tickets for Prisma Compute issues?

Yes, you need the Linear MCP plugin to file bug tracking tickets for Prisma Compute issues, as it handles the required authentication and ticket management across the Prisma product ecosystem required for the workflow.

How does Linear integration work when recording developer experience gotchas?

Linear integration works by automatically filing Triage-state tickets in the appropriate Linear project when a gotcha is recorded, ensuring that the documented developer experience friction is properly triaged and tracked by the product team.

Can I use this workflow to document confusing CLI errors while building Prisma extensions?

Yes, you can use this workflow to document confusing CLI errors while building Prisma extensions by standardizing the capture of symptoms and workarounds, and creating a tracking ticket in one seamless workflow to prevent valuable developer insights from being lost.

What limitations exist when tracking Prisma product issues through Linear ticket creation?

A key limitation when tracking Prisma product issues through Linear ticket creation is the strict dependency on the Linear MCP plugin for authentication and ticket management, meaning the automated upstream creation and triaging workflow cannot function without it.