log_sanitization_v3

Compress verbose VS Code extension logs into concise diagnostics.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/IdanDavidAviv/virgo --skill log-sanitization-v3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log_sanitization_v3
Source: https://github.com/IdanDavidAviv/virgo/tree/main/.agent/skills/log_sanitization_v3
Command: npx skills add https://github.com/IdanDavidAviv/virgo --skill log-sanitization-v3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Log Sanitization Protocol provides a compact, deterministic approach to reducing verbose internal logs and preserving critical information for debugging VS Code extensions. It ensures arrays longer than 10 items are summarized, paths and UUIDs are compressed, and a high-density shorthand format is used for readability, while safeguarding user-facing text with dedicated guards.

Core Features & Use Cases

  • Recursive Summarization: Replace large arrays with concise summaries like [COUNT: n items].
  • Path & UUID Compression: Shorten file paths and identifiers to save horizontal space in logs.
  • High-Density Formatting: Use compact [COMMAND] style lines for log payloads without sacrificing essential content.
  • Cross-Bridge Consistency: Mirror sanitizer logic between Extension (Backend) and Webview (Frontend) for consistent diagnostics.
  • Safety Guards: Preserve verbatim user-facing content through read_aloud_injection_guard and suppress non-essential heartbeat messages.

Quick Start

Enable the log sanitizer in your VS Code extension's diagnostic pipeline to summarize long arrays and compress paths during internal logging.

Frequently Asked Questions about log_sanitization_v3

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compress verbose VS Code extension logs for debugging?

Compress verbose VS Code extension logs by applying recursive array summarization, path and UUID compression, and high-density shorthand formatting to produce concise, readable diagnostics without losing critical state information.

What is recursive array summarization in log sanitization?

Recursive array summarization in log sanitization replaces large arrays longer than ten items with concise shorthand summaries like [COUNT: n items], ensuring logs remain readable while debugging complex extension states.

How do I shorten file paths and UUIDs in diagnostic logs?

Shorten file paths and UUIDs in diagnostic logs using path and UUID compression techniques that reduce horizontal space usage while preserving the essential identifier information needed for debugging.

Can I sanitize logs consistently across VS Code extension backend and webview frontend?

Yes, you can sanitize logs consistently across VS Code extension backend and webview frontend by mirroring sanitizer logic between both layers, ensuring cross-bridge consistency for reliable diagnostics.

How do I prevent user-facing content from appearing in sanitized logs?

Prevent user-facing content from appearing in sanitized logs by implementing safety guards like read_aloud_injection_guard that preserve verbatim content for user-facing segments while suppressing non-essential heartbeat messages.

When should I use log sanitization for VS Code extension debugging?

Use log sanitization for VS Code extension debugging when dealing with complex extension states involving large arrays, long file paths, and identifiers where logs must remain readable without exposing user-facing content.