skills.rest
chrisagrams
chrisagramsCOMMUNITY
Explore all skills by this author →
GitHub

valgrind-summarizer

Parse Valgrind Memcheck logs into compact Markdown summaries.

2|Updated Dec 21, 2021
Search Tags:#log-analysis#valgrind#markdown-report#memory-leaks#memcheck#heap-summary#leak-summary
One-click install
npx skills add https://github.com/chrisagrams/mscompress --skill valgrind-summarizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: valgrind-summarizer
Source: https://github.com/chrisagrams/mscompress/tree/main/.claude/skills/valgrind-report
Command: npx skills add https://github.com/chrisagrams/mscompress --skill valgrind-summarizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Valgrind Memcheck reports can be lengthy and hard to scan. This Skill converts those reports into compact, action-ready Markdown summaries, highlighting heap usage, leak classifications, and top leak sources for quick review.

Core Features & Use Cases

  • Parses Valgrind outputs (.txt, .log, .valgrind) to extract heap and leak metrics.
  • Filters runtime and internal frames to surface user code and actionable results.
  • Generates a readable Markdown report suitable for inclusion in CI reports, issue threads, or documentation.
  • Use Case: you receive a long Memcheck log after a test run and need a concise summary of memory leaks and locations.

Quick Start

Run the bundled parser on a Valgrind log to produce a Markdown summary.

Frequently Asked Questions about valgrind-summarizer

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

FAQPage Schema
How do I summarize a Valgrind Memcheck log into a readable report?▼

To summarize a Valgrind Memcheck log, you can use a parser that strips PID prefixes, extracts heap and leak statistics, deduplicates call stacks, and outputs a structured Markdown document for quick review.

What is the best way to extract memory leak locations from a Valgrind output file?▼

The best way to extract memory leak locations from Valgrind output is to parse the log by filtering runtime and internal frames, which surfaces user code and highlights top leak sources across projects.

Can I generate a Markdown summary from a .valgrind log file for CI pipelines?▼

Yes, you can generate a Markdown summary from a .valgrind log file that is suitable for inclusion in CI reports, issue threads, or documentation by extracting heap usage and leak classifications.

Does the Valgrind log parser handle duplicate call stacks in memory leak reports?▼

Yes, the Valgrind log parser handles duplicate call stacks by deduplicating them during extraction, ensuring the resulting Markdown report remains compact and focused on actionable leak sources.

What Valgrind output formats are supported for generating heap and leak summaries?▼

Supported Valgrind output formats include .txt, .log, and .valgrind files, which are parsed to extract heap usage metrics, leak categories, and top leak sources for a concise summary.

Why are my Valgrind Memcheck reports so hard to scan for memory leaks?▼

Valgrind Memcheck reports are hard to scan because they are lengthy and verbose, but parsing them into a compact Markdown summary highlights heap usage, leak classifications, and top leak sources for quick review.

Related Skills

Explore More Software Engineering Skills→
kzahedikzahedi
3

check-memory-leaks

Run valgrind to detect memory leaks and errors in YARS.

Community
Advanced
KiloforgeKiloforge
2

kf-report

Analyze Kiloforge tracks and git history to generate reproducible Markdown project health reports.

Official
Advanced
mohitmishra786mohitmishra786
159

valgrind

Detect memory errors and profile C/C++ programs with Valgrind tools.

Community
Intermediate
greyhaven-aigreyhaven-ai
29

grey-haven-memory-profiling

Identify memory leaks and optimize usage in JavaScript/TypeScript and Python applications.

Community
Intermediate