codesize

Analyze code and data footprint of embedded firmware from linker map files, ELFs, and static libraries.

5|5|Updated Apr 11, 2026

Search Tags:#analysis #firmware #embedded #ci-cd #symbol-analysis #codesize #map-file

Ready to run

npx skills add https://github.com/open-vela/.claude --skill codesize

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codesize
Source: https://github.com/open-vela/.claude/tree/main/skills/codesize
Command: npx skills add https://github.com/open-vela/.claude --skill codesize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyzes and quantifies the code and data footprint of embedded firmware to help identify opportunities to shrink binary size and memory usage.

Core Features & Use Cases

Symbol-level size breakdown across ARM, Xtensa, and RISC-V targets.
Per-library statistics with top consumers and actionable optimization hints.
CI-friendly outputs in Markdown/JSON/CSV for automated reviews and dashboards.

Quick Start

Run a size analysis on your build artifacts and review the largest modules to guide firmware size optimization.

Frequently Asked Questions about codesize

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

FAQPage Schema

How do I analyze firmware size from linker map files and ELF binaries?▼

To analyze firmware size, you can use this Skill to process linker map files, ELFs, and static libraries. It identifies and quantifies the code and data footprint of embedded firmware across ARM, Xtensa, and RISC-V targets.

What is the best way to identify large modules in a multi-core NuttX project?▼

Identifying large modules in a multi-core NuttX project requires a symbol-level size breakdown. This Skill provides per-library statistics and actionable optimization hints by analyzing build artifacts across multi-core targets.

Can I automate firmware size analysis in a CI workflow?▼

Yes, you can automate firmware size analysis in a CI workflow. This Skill provides CI-friendly outputs in Markdown, JSON, and CSV formats, enabling automated reviews and dashboards to compare firmware versions.

Does this symbol analysis tool support RISC-V and Xtensa architectures?▼

Yes, this symbol analysis tool supports RISC-V and Xtensa architectures, alongside ARM targets. It applies to multi-core Vela and NuttX projects to provide a comprehensive code and data footprint breakdown.

What file formats do I need to perform a symbol-level size breakdown?▼

To perform a symbol-level size breakdown, you need linker map files, ELF binaries, and static libraries such as .map, .elf, and .a files. These build artifacts are required to quantify the firmware footprint.

Why does my embedded firmware binary keep growing and how do I locate the top consumers?▼

Your embedded firmware binary may be growing due to large libraries or symbols. This Skill analyzes your build artifacts to provide per-library statistics, locate top consumers, and offer actionable optimization hints.