菜单
Adds structured logging to a module or service, including log levels, context fields, correlation IDs, and PII masking. Do NOT use for error handling design, metrics/tracing instrumentation, or log aggregation setup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use to implement a REST or GraphQL API endpoint from a specification or description, including request validation, error handling, and accompanying tests. Activate for building a new API route, resolver, or handler end-to-end. Do NOT use for API design/contract creation, documentation generation, or frontend API consumption.
Use to implement background job processing with a queue, worker, retry with exponential backoff, dead letter queue, and monitoring. Activate when the request involves offloading work from the request cycle (emails, reports, data processing). Do NOT use for real-time event streaming, webhook handling, or scheduled cron jobs.
Use to scaffold a new project from scratch — generating directory structure, configuration files, entry points, and a README skeleton. Activate when starting a new project, service, or package and needing a production-ready starting point. Do NOT use for adding features to existing projects, generating tests, or CI/CD configuration.
Use to design and implement a caching layer for data that is expensive to compute or fetch. Activate for cache-aside, write-through, or write-behind patterns, TTL strategy, and cache invalidation logic. Do NOT use for database query optimization, CDN configuration, or HTTP response caching headers.
Use to generate a CI/CD pipeline configuration for building, testing, and deploying an application. Activate for GitHub Actions, GitLab CI, CircleCI, or similar pipeline tools for any tech stack. Do NOT use for infrastructure provisioning, Dockerfile creation, or deployment strategy design.
Use to generate production-ready code for a new feature, function, class, or module from a description. Activate for writing new code from scratch with error handling, inline documentation, and a self-review checklist. Do NOT use for refactoring existing code, code review, or test generation.
| name | logging-instrumentation |
| description | Adds structured logging to a module or service, including log levels, context fields, correlation IDs, and PII masking. Do NOT use for error handling design, metrics/tracing instrumentation, or log aggregation setup. |
| version | 1.1.0 |
| time_saved | Manual: 2–3 hours | With skill: 15–20 minutes |
| license | Proprietary — Personal Use Only |
| category | coding |
| complexity | Intermediate |
| tokens | ~3000 |
| tags | ["logging","observability","structured-logs","correlation-id","pii-masking"] |
| author | vheins |
Add production-quality structured logging with context, tracing, and data protection to any module.
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | Stack + Library (e.g., "Node.js + pino") |
module_code | string | Yes | Source code to instrument |
log_requirements | string | Yes | Events, fields, and masking policies |
LOG_LEVEL environment checks, and ISO timestamps. Include service/version/env as default fields.| Case | Strategy |
|---|---|
| High-frequency loops | Use DEBUG or apply sampling; avoid per-iteration INFO. |
| Async boundaries | Use stack-specific propagation (AsyncLocalStorage/contextvars). |
| 3rd-Party libs | Map external logs to the internal JSON format and Correlation IDs. |
flowchart TD
A([Start: Logging Instrumentation]) --> B[Analyze module code & log requirements]
B --> C[Configure JSON logger, LOG_LEVEL, ISO timestamps]
C --> D[Identify significant events]
D --> E{Event type?}
E -- Unexpected error --> F[LOG ERROR with full context]
E -- Recoverable/degradation --> G[LOG WARN]
E -- Business event --> H[LOG INFO]
E -- Trace details --> I[LOG DEBUG (disabled in prod)]
E -- Hot path --> J[Skip or apply log sampling]
F & G & H & I & J --> K[Inject correlation ID at entry point]
K --> L{Async context?}
L -- Node.js --> M[AsyncLocalStorage]
L -- Python --> N[contextvars]
L -- Go --> O[context.Context]
M & N & O --> P[Include correlation ID in all logs]
P --> Q[Identify sensitive fields]
Q --> R{Field type?}
R -- Password/key --> S[Mask: ***]
R -- Email --> T[Partial mask: j***@example.com]
R -- Credit card --> U[Last 4: ****1234]
S & T & U --> V{High volume?}
V -- Yes --> W[Apply sampling (1 in N)]
V -- No --> X([Output: Instrumented module code])
W --> X
@upstash/context7-mcp: Library documentation and examples.| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-03-20 | Restructured: moved examples/references, added compatibility/license |
| 1.0.0 | 2026-03-20 | Initial release |