Library / Checkups / Error Tracking and Logs Checkup
Player 12, Error Tracking and Logs Checkup

Error Tracking and Logs Checkup

CheckupLayer 12 · Error Tracking & LogsHelps every agent we tested.

Your agent learns to check that every crash is caught, reported with context and shown as a plain message.

Your agent reads the app entry points, layouts, endpoints, background jobs and every error handler, then checks that tracking runs in both browser and server, no failure is swallowed, a crash takes down one section instead of the whole app, reports carry the page and user, logs are structured and ranked by business impact, reports point to real file names and no private data lands in logs. It fixes what is safe to fix in code and reports the rest. It tells you to trigger a test error on the live app and confirm an alert arrives, set alert rules in your tracking dashboard and replace any secret that was written to logs.

100 tokens
Owned
Buy for 100 tokens Download

Spend 100 tokens on Error Tracking and Logs Checkup? You have 350 tokens.

You need 50 more tokens.

Get tokens

Bought. It's in your Library.

Token purchases are final. Tokens do not expire and can be used at any time.

Your first skill is on us. Every new account starts with 100 welcome tokens.

A look inside

# Layer 12: Error Tracking and Logs Checkup

## Standard
Eight checks, every time, across the whole repository. Each one gets a pass or fail with the file that proves it. An app with no error reports is treated as an app with no error tracking, not an app with no bugs. Fix what is safe to fix in code and report what only the builder can do in a dashboard.

## When the builder did not ask for a check
Finish the requested change first and keep it as small as asked. Then run the procedure below across the app as a read-only check. Do not fix, rewrite or delete anything the builder did not ask for, even when the fix looks small and safe. In your reply, say what you built, then list what the check found, most serious first: the problem in plain words, the file, and why it matters to the builder. Then ask the builder whether you should fix them, and stop. Fix only after the builder says go.

## Procedure
Read the app entry points for browser and server, the root layout and every route-level layout, every API route and background job, every `try`/`catch` and promise `.catch`, every `console.` call, the build config and the deploy scripts. Then check all eight.

How to use it

  1. Download the file.
  2. Add it to whatever agent you build with.
  3. Ask your agent to run it.

Checkups also run on their own when your agent works on that layer. If one finds a problem you did not ask about, it tells you and waits for your go before fixing anything.

Learn the method free

This skill comes out of a free course in the community: The Foundation, Layer 12: Error Tracking & Logs.

Packs that include this skill

The Full Squad
All 13 Checkups, one for every layer of your app.
1,300 1,040 tokens

Version 1.0.0 · Last updated November 14, 2026