What problem does it solve? Locating the code behind lci's installers, self-update, status/debug commands, profiling flags, and release packaging is hard because it spans the CLI tree, updater, server routes, CMake presets, and CI workflows. This skill provides a verified code map with file:line references plus the evidence needed to compare lci's install footprint against other code tools. ## Core Features & Use Cases - Surface and code map: Entry points for lci update, status, list, debug info/export/memprofile, gperftools profiling flags, install scripts, CPack/npm/pip packaging, and CI legs, each with exact source locations. - Invariants and traps: Documents fail-fast stubs (debug validate/deps/graph), updater string-equality version comparison, release-binary dependency traps, and memprofile attribution pitfalls. - Probe recipes and product comparison: Shell commands to exercise every surface, plus comparison axes (binary size, runtime deps, self-update, platform matrix) against ripgrep, ctags, Zoekt, and Sourcegraph. - Use Case: When asked whether lci's release binary is self-contained or how its footprint compares to ripgrep, use this skill to find the CPack config, run ldd on the binary, and cite verified numbers instead of guessing. ## Quick Start Use the lci-ops-diagnostics skill to find where lci's self-update and status commands are implemented and verify the release binary's runtime dependencies.
