Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Sign in
Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

A page, a video or an image online.

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Find the cause of a production error v1.0.0

Use this resource to find the cause of a production server error and file the issue

New

  • 364 downloads
  • 233 likes
  • 150 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install trace-production-error-cause

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent tallies 5xx errors by route in local logs, then reads the exception and stack in Sentry. It names the PR that caused the regression, reproduces it on the shipped runtime and files the issue.

Mostly picked by

Updated November 2, 2026

Card for the “Find the cause of a production error” skill

Details

Works in
Install guides
Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md: method for reading local logs and Sentry together
  • SKILL.md: regression naming, reproduction and filing steps

Good fit for

  • A user sees an opaque 500 error in a shipped build
  • One route's error rate spikes after an update

Not for

    Tags

    • error
    • sentry
    • production

    About

    You say

    “Users are getting a 500 error on the latest build, find the cause.”

    Card for the “Find the cause of a production error” skill

    Skill published by different-ai under the MIT license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to find the cause of a production server error and file the issue
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE1.8 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • SKILL.md3.2 KB

    Origin and licence

    Listed unmodified

    Author
    different-ai
    Source
    github.com/different-ai/openwork/tree/707bb83bcb90b2dd8a27a5d6028a896d6f43ffaf/.opencode/skills/hunt-a-prod-error
    Licence
    MIT

    Notice

    « hunt-a-prod-error » (different-ai, MIT) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.