All SkillsGet Started Free
Ln 627 Diagnosability Auditor
Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.
MCP get_skill({ skillId: "ln-627-diagnosability-auditor-3b414baf" })Use this skill with your agent
Create a free account and connect via MCP
> **Paths:** File paths (`references/`, `../ln-*`) are relative to this skill directory.
# Diagnosability Auditor (L3 Worker)
**Type:** L3 Worker
Specialized worker auditing whether operators can diagnose incidents.
## Purpose & Scope
- Audit **diagnosability** (Category 10: Medium Priority)
- Check structured logs, metrics, tracing, correlation IDs, and log levels
- Emit `ADD_DIAGNOSTIC_SIGNAL`, `STRUCTURE_LOGS`, or `PROPAGATE_CORRELATION`
- Calculate compliance score (X/10)
## Inputs
**MANDATORY READ:** Load `references/audit_worker_core_contract.md`.
Tool policy: follow host AGENTS.md MCP preferences; load `references/mcp_tool_preferences.md` and `references/mcp_integration_patterns.md` only when host policy is absent or MCP behavior is unclear.
Receives `contextStore` with tech stack, framework, codebase root, output_dir.
Use `hex-graph` first when traces, call paths, or cross-file references materially improve the audit. Use `hex-line` first for local code reads when available. If MCP is unavailable, unsupported, or not indexed, continue with built-in `Read/Grep/Glob/Bash` and state the fallback in the report.
## Workflow
Detection policy: use two-layer detection (candidate scan, then context verification); load `references/two_layer_detection.md` only when the verification method is ambiguous.
1) Parse context + output_dir
2) **Determine project type (Layer 2 pre-check):** Is this a web service (all checks apply), CLI tool (health/probes not applicable), or library (most checks optional)? Adjust applicable checks accordingly.
3) Check observability patterns (Layer 1: grep)
4) Analyze context per candidate (Layer 2):
- Structured logging: is this a library (no logging OK) or a service (logging required)?
- Request tracing: monolith -> less needed. Microservice -> critical
5) Collect confirmed findings
6) Calculate score
7) **Write Report:** Build full markdown report in memory per `references/templates/audit_worker_report_template.md`, write to `{output_dir}/ln-627--global.md` in single Write call
8) **Return Summary:** Return minimal summary
## Audit Rules
### 1. Structured Logging
**Detection:**
- Grep for `console.log` (unstructured)
- Check for proper logger: winston, pino, logrus, zap
**Severity:**
- **MEDIUM:** Production code using console.log
- **LOW:** Dev code using console.log
#agile-workflow#code-review#debuggingbash