القائمة
Analyze log files by stripping ANSI escape sequences first. Use when asked to process, handle, read, or analyze log files that may contain terminal escape codes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | analyze-log-files |
| description | Analyze log files by stripping ANSI escape sequences first. Use when asked to process, handle, read, or analyze log files that may contain terminal escape codes. |
.log or log-related files that may contain ANSI escape sequencesLog files captured from terminal sessions often contain ANSI escape sequences for:
\x1b[31m for red)These sequences make logs difficult to:
Before analyzing any log file, first strip the ANSI sequences using ansifilter:
ansifilter -i /tmp/r3bl_tui/log.txt -o /tmp/clean_log.txt
For other log file names, adjust accordingly:
ansifilter -i <input_file> -o /tmp/clean_log.txt
Read and analyze /tmp/clean_log.txt instead of the original file:
# Use the Read tool on /tmp/clean_log.txt
When reporting findings to the user:
/tmp/r3bl_tui/log.txt - General purpose log in project roottarget/ - Cargo build logs/tmp/*.log - Temporary logsUser: "Can you analyze /tmp/r3bl_tui/log.txt and tell me what's wrong?"
ansifilter -i /tmp/r3bl_tui/log.txt -o /tmp/clean_log.txt/tmp/clean_log.txtIf ansifilter is not installed:
# Ubuntu/Debian
sudo apt-get install ansifilter
# macOS
brew install ansifilter
# Or run bootstrap.sh to install all dependencies
./bootstrap.sh
check-code-quality - For checking Rust code quality (may generate logs)analyze-performance - For performance analysis (generates flamegraph data)/analyze-logs - Explicitly invokes this skillRun comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.
Enforce the "Clean Imports over Inline Absolute Paths" rule by removing inline crate:: prefixes and adding proper use statements.
Rules and guidelines for creating well-formatted commit messages, including 72-char limits, scope prefixes, and trailer blocks for tasks, PR closing, and attribution.
Zero-allocation string building strategies. Use when formatting strings, generating ANSI codes, or writing hot loops to avoid heap allocations and Formatter state machine overhead.
Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns. Use after code changes and before creating commits.
Standard for writing structured tracing logs behind debug flags.