util-logging

Included with Lifetime

$97 forever

Add, fix, or update logging in project code

Code Review

What this skill does

## Logging Scope
$ARGUMENTS

---

Add, fix, or update logging following strict principles.

## Core Principle: Signal over Noise

Logs that don't get read are useless. Every log statement must earn its place.

**Before adding a log, ask:**
- Will someone look at this?
- Does this help diagnose something?
- Is this the right level?
- Is there already a log covering this?

Cut ruthlessly. Then cut more.

## Log Levels

### 1. INFO: The Service Narrative
**What the service is doing at a glance.**

Log these:
- Service startup/shutdown
- External connections established/closed (WebSocket, DB)
- Subscriptions to new resources
- Periodic heartbeats (every N seconds: "processing X markets")
- HTTP requests going out (target, method)
- Key state transitions

Never log:
- Every function entry/exit
- Internal data transformations
- Things that happen thousands of times per second

### 2. DEBUG: Granular Internals
**Details for troubleshooting. Off in production unless investigating.**

Log these:
- Request/response payloads (redact secrets)
- Internal state changes
- Timing breakdowns
- Configuration values at startup
- Loop iterations when relevant

### 3. WARN: Rare by Design
**Recoverable errors you're explicitly allowing to continue.**

Log these:
- Fallback to default config
- Retryable failures that succeeded on retry
- Resource thresholds approached (memory at 80%)
- Deprecated API usage detected

Never log:
- Expected conditions (user not found, validation failed)
- Anything you'd ignore in production

### 4. ERROR: Every Failure
**Log at the handling point. Once.**

- Use language/framework hooks to catch all errors automatically
- Include context: what was being attempted, relevant IDs
- Don't log and rethrow—pick one
- Stack traces for unexpected errors

## Process

1. Identify scope (file, module, or all)
2. Audit existing logging against these levels
3. Add missing INFO logs for external-facing events
4. Remove noisy/redundant logs
5. Ensure ERRORs are logged at handling points
6. Use framework-provided logging (HTTP interceptors, etc.) where available
7. **Remind: run `/logging` after significant code changes**

## No Scope Specified?

Review ALL logging against current code. Fix level mismatches. Remove noise. Add missing service narrative. Report what was changed.

Files: 1

Size: 2.4 KB

Complexity: 9/100

Category: Code Review

Source: https://github.com/jsai23/claude-tooling/tree/main/compiled/util/agentskills/util-logging

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts