Skill: backend/observability-audit

Skill: backend/observability-audit

Purpose

Improve and standardize observability so the system is operable after changes:

• logs: structured, queryable, minimal but sufficient
• metrics: counters/timers/gauges for key outcomes
• traces: propagation and spans where available
• audit: records for sensitive actions when required

This skill is a pass over changed behavior, not feature work.

Inputs

• Changed components/endpoints/jobs
• Risk posture (from repo docs/profile if present)
• Observability standards (from REPO_PROFILE.json if present)
• Correlation/id propagation standard (if any)

Outputs

• Improved logging:
  • include correlation id
  • include primary identifiers (request id, user id where safe, entity id)
  • include outcome + error codes
• Metrics updates if repo uses them:
  • success/fail counters
  • latency timing
  • queue depth / retries (for jobs)
• Tracing spans or propagation fixes if repo uses tracing
• Audit entries for protected actions if applicable

Non-goals

• Implementing business logic
• Adding heavy instrumentation everywhere
• Logging secrets or sensitive payloads