Back to Details

cco-shield

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ContextShield Status

ContextShield状态

Show the user the current ContextShield protection status and historical waste prevention stats.
Run the following command to get pattern data:
bash
node ${CLAUDE_PLUGIN_ROOT}/src/tracker.js patterns
From the patterns data, present:
  1. ContextShield Status: Active (it's always active as a PreToolUse hook)
  2. Protected Files: List files with 3+ waste sessions — these trigger warnings before Read
  3. Tokens Saved: Estimate based on waste history (files that would have been read without shield)
  4. Co-occurrence Groups: Files that are usually edited together
Format as a clean status report. If no pattern data exists yet, tell the user: "ContextShield is warming up! It learns from your usage patterns and will start giving you smart suggestions after a few sessions."
End the report with:
ContextShield runs automatically on every Read. No configuration needed.
向用户展示当前ContextShield的保护状态以及历史防浪费统计数据。
运行以下命令获取模式数据：
bash
node ${CLAUDE_PLUGIN_ROOT}/src/tracker.js patterns
从模式数据中展示以下内容：
  1. ContextShield状态：已激活（它作为PreToolUse钩子始终处于激活状态）
  2. 受保护文件：列出存在3次及以上浪费会话的文件——这些文件在读取前会触发警告
  3. 已节省Tokens：基于浪费历史估算（即如果没有防护盾会被读取的文件）
  4. 共现组：通常会被一起编辑的文件
将内容整理为清晰的状态报告。如果尚无模式数据存在，请告知用户： "ContextShield正在预热中！它会从你的使用模式中学习，经过几次会话后将开始提供智能建议。"
报告结尾添加：
ContextShield会在每次读取时自动运行，无需配置。