modem-dev/ossrules / public/files/rustfs/.agents/skills/rustfs-logging-governance
rustfs-logging-governance
UnverifiedAdd or review RustFS `tracing` events with the repository field shape, level policy, privacy boundaries, and guardrails. Use when a change adds or edits a tracing macro/instrumentation site or the logging guardrail script.
RustFS Logging Governance
Apply this skill only to changed logging sites; do not turn a local log edit into a broad logging cleanup.
Workflow
- Read the changed function/module context and classify the site as lifecycle, request/hot path, fallback, external fetch, or summary.
- Match neighboring structured events and reuse existing
EVENT_*,LOG_COMPONENT_*, andLOG_SUBSYSTEM_*constants. - Put stable fields first (
event,component,subsystem,state/result, then context) and a short label last. - Select the level by operational meaning:
error: behavior/security-affecting failure;warn: degraded/fallback/operator-actionable state;info: low-frequency lifecycle/mode change;debug: targeted diagnostics;trace: repetitive request/object/shard success paths.
- Never log secrets, tokens, auth headers, credential payloads, raw
attacker-controlled bodies, or merged config dumps. Error strings and
Debugoutput are log surfaces too. - Prefer one aggregate summary over inventories or startup banners.
- Run
./scripts/check_logging_guardrails.shand the checks selected by rootAGENTS.md.
Read logging-governance.md only for a broad logging audit, event-model migration, or guardrail expansion. Ordinary single- site edits do not require the full workspace scope map.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |