akiselev

Reference documentation for analyzing Claude Code conversation history files

Invoke IMMEDIATELY via python script when user requests codebase understanding, architecture comprehension, or repository orientation. Do NOT explore first - the script orchestrates exploration.

Invoke IMMEDIATELY via python script to stress-test decisions and reasoning. Do NOT analyze first - the script orchestrates the critique workflow.

Invoke IMMEDIATELY via python script when user requests structured reasoning for open-ended analytical questions. Do NOT explore first - the script orchestrates the thinking workflow.

Detect and resolve incoherence in documentation, code, specs vs implementation.

Interactive planning and execution for complex tasks. Use when user asks to use or invoke planner skill.

Invoke IMMEDIATELY via python script when user requests problem analysis or root cause investigation. Do NOT explore first - the script orchestrates the investigation.

Invoke IMMEDIATELY via python script when user requests prompt optimization. Do NOT analyze first - invoke this skill immediately.

Audit the altium-cli codebase for data integrity issues: silent data corruption, dropped fields, overwritten values, raw byte passthrough, untyped parameter forwarding, and deserialization shortcuts. Activate when the user requests a data review, data integrity audit, or wants to verify that no data is silently lost or corrupted. Can target the full codebase, specific crates, or specific files.

Audit the altium-cli codebase (or a specified scope) against project rules from CLAUDE.md. Activate when the user requests a rules review, rules check, compliance audit, or codebase audit. Checks for: fail-fast violations, raw type usage, privacy leaks across crate boundaries, silent error suppression, unconsumed data skipping, missing domain types, and error handling correctness. Can target the full codebase, specific crates, files, or git changes.

Control the AutoPCB Shell GUI programmatically via CLI commands. Use for visual validation, UI testing, screenshot-driven workflows, opening files/projects, navigating panels, selecting components, and verifying GUI state through screenshots. Activate when the user requests: - GUI interaction or automation - Visual validation or screenshot comparison - Opening files or projects in the GUI - Selecting components or nets in the PCB/schematic view - Toggling panels, sidebars, or layout changes - UI testing or smoke testing the shell

Use ghidra-cli for reverse engineering tasks: binary analysis, decompilation, function inspection, cross-reference analysis, pattern discovery, and binary patching. Activate when the user requests: - Binary analysis or reverse engineering - Decompilation or disassembly - Function listing, inspection, or renaming - Cross-reference or call graph analysis - String or byte pattern searches - Binary patching or modification - Ghidra project management

Cross-reference the altium-cli code (types, constants, records, parsing) against the reverse-engineered documentation in docs/dxp/, docs/schlib/, docs/schdoc/, docs/pcblib/, and the Altium C#/.NET source in ./AD26-dotnet/. Finds mismatches, missing implementations, wrong values, ambiguous specs, and documentation drift. Asks the user to resolve ambiguity rather than guessing.

Use ilspy-cli for .NET assembly decompilation and analysis. Produces clean C# source from .NET IL bytecode. Activate when the user requests: - .NET assembly decompilation - .NET type or method inspection - Detecting whether a binary is .NET or native - Searching decompiled .NET source code - Assembly metadata inspection Prefer ilspy-cli over ghidra-cli for .NET binaries (ghidra produces poor output for .NET IL).

Use ghidra-cli for reverse engineering tasks: binary analysis, decompilation, function inspection, cross-reference analysis, pattern discovery, binary patching, and type system management. Activate when the user requests: - Binary analysis or reverse engineering - Decompilation or disassembly - Function listing, inspection, or renaming - Cross-reference or call graph analysis - String or byte pattern searches - Binary patching or modification - Ghidra project management - Type management (structs, enums, typedefs, struct fields) - Function signature editing (return type, calling convention, full signature) - Variable retyping in decompiled functions

Use ghidra-cli for reverse engineering tasks: binary analysis, decompilation, function inspection, cross-reference analysis, pattern discovery, and binary patching. Activate when the user requests: - Binary analysis or reverse engineering - Decompilation or disassembly - Function listing, inspection, or renaming - Cross-reference or call graph analysis - String or byte pattern searches - Binary patching or modification - Ghidra project management

Find non-exact code duplication with decombine (tree-sitter + local embeddings + SQLite). Use when asked to find duplicate/copy-pasted/similar code in a codebase, audit a rewrite against the original, semantically search indexed code, or run/interpret any decombine command. Covers setup, the duplicates workflow, and (in reference files) comparison, semantic query, concerns, and operations.