Agent Skills › rustfs/rustfs › rustfs-logging-governance

rustfs-logging-governance

GitHub

指导在 RustFS 中添加或审查 tracing 日志，确保符合字段规范、级别策略及隐私边界。适用于修改追踪宏或运行守卫脚本的场景，强调不滥用清理且需通过自动化检查。

.agents/skills/rustfs-logging-governance/SKILL.md rustfs/rustfs

Trigger Scenarios

添加或编辑 RustFS tracing 宏/监控点运行 logging guardrail 脚本

Install

npx skills add rustfs/rustfs --skill rustfs-logging-governance -g -y

More Options

Non-standard path

npx skills add https://github.com/rustfs/rustfs/tree/main/.agents/skills/rustfs-logging-governance -g -y

Use without installing

npx skills use rustfs/rustfs@rustfs-logging-governance

指定 Agent (Claude Code)

npx skills add rustfs/rustfs --skill rustfs-logging-governance -a claude-code -g -y

安装 repo 全部 skill

npx skills add rustfs/rustfs --all -g -y

预览 repo 内 skill

npx skills add rustfs/rustfs --list

SKILL.md

Frontmatter

{
    "name": "rustfs-logging-governance",
    "description": "Add 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_*, and LOG_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 Debug output are log surfaces too.
Prefer one aggregate summary over inventories or startup banners.
Run ./scripts/check_logging_guardrails.sh and the checks selected by root AGENTS.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.