Agent Skills
› rustfs/rustfs
› rustfs-logging-governance
rustfs-logging-governance
GitHub用于审查和添加 RustFS 追踪事件,规范字段结构、日志级别及隐私边界。通过运行检查脚本确保符合治理规范,防止敏感信息泄露。
Trigger Scenarios
修改或新增 tracing 宏/日志点
执行日志治理脚本检查
Install
npx skills add rustfs/rustfs --skill rustfs-logging-governance -g -y
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_*, 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.
Version History
-
0fe41da
Current 2026-08-29 02:10
重构工作流程,细化站点分类与字段排序规则;强调隐私安全边界,限制对引用文档的访问范围以优化性能。
- 0d129ec 2026-08-20 14:32


