logging

Standardize Fastify request logging and business audit trails in TypeScript monorepos.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/alissonmds00/LostPets.v2 --skill logging-alissonmds00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging
Source: https://github.com/alissonmds00/LostPets.v2/tree/main/.claude/skills/logging
Command: npx skills add https://github.com/alissonmds00/LostPets.v2 --skill logging-alissonmds00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of consistency in request logging and business auditing, ensuring that all system interactions are tracked securely without exposing sensitive user data.

Core Features & Use Cases

  • Access Logging: Standardizes Fastify request/response logging using Pino, ensuring request IDs are tracked across the system.
  • Audit Trail: Provides a structured approach to recording sensitive business operations (e.g., identity changes) via a dedicated AuditLog service.
  • Use Case: When implementing a new sensitive feature like user onboarding, use this skill to ensure the action is correctly recorded in the AuditLog repository for future investigation.

Quick Start

Ask the AI to apply the logging convention to a new route or to implement an audit log entry for a specific business action.

Frequently Asked Questions about logging

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

FAQPage Schema
How do I standardize request logging and audit trails in a Fastify TypeScript backend?

You can standardize request logging and audit trails by applying centralized Pino serializers for Fastify requests and a dedicated AuditLog service layer for persistent business event tracking.

How does request correlation work with Pino logging in a Fastify application?

Request correlation works by tracking request IDs across the system using standardized Pino serializers, ensuring every Fastify request and response interaction is linked for observability.

What is the best way to implement sensitive data redaction for backend audit logs?

The best way to implement sensitive data redaction is by enforcing centralized logging serializers that securely track system interactions without exposing sensitive user data in the audit trails.

Does this logging approach support regulatory compliance requirements for business auditing?

Yes, regulatory compliance is supported by providing a structured AuditLog service layer that records sensitive business operations, satisfying observability and compliance requirements for future investigation.

How do I record an audit log entry for a specific business action in a Prisma monorepo?

To record an audit log entry, ask the AI to implement an audit log entry for your specific business action, ensuring it is correctly saved in the AuditLog repository within your Prisma monorepo.