All skills
logging-error-handling
FoundationJIT onlytask-agent/review-agent: use when structured errors, logs, correlation, redaction, propagation, or safe diagnostics change; skip when logging/error handling is unaffected.
- Group
- Backend engineering
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- design structured errors logging context propagation and safe diagnostics
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local logging error handling decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- logging and error decision with ownership, external meaning, diagnostic events, correlation, outcome classification, redaction, volume bounds, reconstruction evidence, unverified paths or sinks, proof limits, and residual risk
- accepted audit-contract dependency or named
logging-design-gate/security-privacy-gatehandoff for each security-relevant outcome; do not claim protected audit-record closure from diagnostic-log evidence
Escalation signals
When this skill must hand the decision back
- Poor errors and logs slow diagnosis or leak sensitive data
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | log schema correlation redaction or error mapping choices remain unresolved | existing logging policy selects fields levels and client contract | TaskReview |
| checklist.mddecision-checklist | change affects error taxonomy correlation redaction audit or retry context | no logging sink or client-error behavior changes | TaskReview |
| evidence-patterns.mdevidence-pattern | redaction correlation audit or error-mapping claims need fresh proof | current fixtures and captured outputs prove each logging claim | TaskReview |