What is dead-code-analysis?

A command that checks which parts of kicad-sch-api, a Python library for KiCad schematic files, are actually used when the software runs. It exercises the library’s features and records the functions that were called.

Use it to analyze the full project or a selected script, run broad functionality checks, and produce logs and lists of observed function calls.

It helps distinguish genuinely unused code from code that is only missed by ordinary tests or searches.

How circuit-synth/kicad-sch-api configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to circuit-synth/kicad-sch-api. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/circuit-synth/kicad-sch-api/main/.claude/commands/dev/dead-code-analysis.md

Clone the repo

git clone --depth 1 https://github.com/circuit-synth/kicad-sch-api

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/circuit-synth/kicad-sch-api/dead-code-analysis/github.svg)](https://agentmods.dev/commands/circuit-synth/kicad-sch-api/dead-code-analysis)

Your own site

<a href="https://agentmods.dev/commands/circuit-synth/kicad-sch-api/dead-code-analysis"><img src="https://agentmods.dev/badge/commands/circuit-synth/kicad-sch-api/dead-code-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/circuit-synth/kicad-sch-api/dead-code-analysis"><img src="https://agentmods.dev/badge/commands/circuit-synth/kicad-sch-api/dead-code-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,701 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01701
Opus 5.5	$0.00000	$0.00680
Sonnet 5.5	$0.00000	$0.00340
Haiku 4.5	$0.00000	$0.00170

Measured 2mo ago against content hash 70097a5ab179, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dead-code-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

dead-code-analysis — 100% identical, 0 lines differ
dead-code-analysis — 95% identical, 2 lines differ

.claude/commands/dev/dead-code-analysis.md · 220 lines

How it starts

The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dead Code Analysis Command - kicad-sch-api

Usage

/dead-code-analysis [target-script]

Description

Performs comprehensive dead code analysis for kicad-sch-api by running ALL functionality and observing which functions are actually called. This provides accurate utilization metrics by exercising:

Core Schematic Operations - Load, save, component management, validation
S-Expression Parsing - All parsing and formatting functionality
Component Collections - Filtering, bulk operations, indexing
Symbol Library Management - Caching, discovery, multi-source lookup
MCP Server Integration - All MCP tools and Python bridge
Validation Systems - Error collection, comprehensive validation
Format Preservation - Round-trip testing, exact output matching
Performance Systems - Caching, optimization, benchmarking

Parameters

target-script (optional): Path to script to run for function call analysis. Defaults to comprehensive test suite.
--comprehensive: Runs full system functionality test (default behavior)

Output Files

function_calls.log: Raw debug output from script execution
unique_function_calls.txt: List of unique functions that were called
Dead_Code_Analysis_Report.md: Comprehensive analysis report
*.backup: Backup files for all instrumented source files

Examples

# Analyze dead code using comprehensive test suite
/dead-code-analysis

# Analyze using specific test script
/dead-code-analysis tests/test_comprehensive_operations.py

# Analyze using MCP server test
/dead-code-analysis tests/test_mcp_integration.py

Implementation for kicad-sch-api

The command performs the following automated steps:

1. Function Instrumentation

Scans all Python files in kicad_sch_api/
Adds logging.debug(f"CALLED: {function_name} in {file_path}") to every function
Creates backup files (.backup) before modification
Preserves existing function logic and formatting

Read the full file on GitHub · 220 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 220 lines · 0 tokens per session scan A 70097a5ab179

Subscribe to this mod's changes

dead-code-analysis is a command published in the GitHub repository circuit-synth/kicad-sch-api (57 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,701 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging automation circuits circuits-as-code eda kicad mcp

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

kicad-sch-api: Command for Claude Code