---
author: 'Gustavo Ruiz'
description:
  'Decide and review GFiber service log levels while keeping production INFO
  output bounded and traceable. Use when adding, changing, or auditing service
  logs.'
extras:
  'Add an evaluation fixture for a hot loop, a payload dump, and a correctly
  bounded per-item result line.'
focus:
  'Choose and audit production log levels while keeping INFO volume bounded.'
id: 'gfiber-logging'
improve:
  - 'Make environment-specific assertions, such as DEBUG availability,
    configurable facts with evidence from the deployed project.'
  - 'Package the audit heuristic as a versioned script with fixtures instead of
    leaving it only in prose.'
  - 'Add a stable review output contract: location, proposed level, reason,
    volume risk, and measurement evidence.'
name: 'gfiber-logging'
path: '../submitted-skills/Gustavo%20Ruiz/skills/gfiber-logging/SKILL.md'
status: 'Strong policy package'
title: 'GFiber logging'
wins:
  - 'Excellent level-selection rules, practical cases, and a volume-audit
    workflow.'
  - 'Clear data-minimization and correlation guidance.'
  - 'Supporting references make the policy easy to apply.'
---

# gfiber-logging

## Inputs

Changed paths or service root, the request or flow under review, and the project
logging configuration.

## Workflow

1. Read `references/levels.md` to classify each event; use `references/cases.md`
   for known service patterns.
2. Check new lines for correlation, minimized fields, and bounded volume.
3. Use `references/audit.md` for a static audit; measure representative traffic
   separately when a path is high-volume.
4. Report each finding with evidence and distinguish measured results from risk
   estimates.

## Rules

- Use the approved contextual logger when the project supports one.
- Never log secrets, PII, or full request/response bodies; cap identifier lists.
- Treat INFO caps and DEBUG deployment settings as project configuration facts.
  Report missing evidence rather than assuming them.
- This skill is read-only. Do not edit code or production configuration.

## Output

State the scope, each finding (location, level, reason, volume risk, action),
audit command/results, and any unmeasured risk.
