Claude Code: Software Development Skills

Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview.

Indexes and queries project research graphs backed by hex-research MCP. Use for hypotheses, goals, benchmark runs, evidence depth, derived goal metrics, lineage, generated research maps, and graph audits.

Modernizes a bounded capability by removing obsolete custom mechanisms or reducing bundle and maintenance cost. Use for proven modernization value; not routine upgrades or tuning.

Checks application security boundaries: secrets, injection, XSS, input validation, and sensitive env defaults. Use when auditing exploitable code paths.

Checks build, lint, type, test, and CI delivery gate failures. Use when auditing whether the project can reliably ship.

Checks evidence-backed duplication, over-abstraction, and unused extensibility. Use when auditing DRY/KISS/YAGNI risk.

Checks local maintainability hotspots: complexity, long methods, god modules, signatures, algorithms, and constants. Also flags identifier drift across API/DTO/DB layers. Use when auditing code hotspots.

Checks dependency health and generic custom utility/integration replacement opportunities. Use when auditing dependency and reuse risk.

Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.

Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.

Checks races, deadlocks, async hazards, TOCTOU, blocking I/O, and shared resource contention. Use when auditing concurrency correctness.

Checks runtime lifecycle and config validation: bootstrap, shutdown, probes, cleanup, env sync, and fail-fast startup. Use for runtime readiness.

Audits assertion strength and test oracles that prove real defects. Use when finding weak tests that execute code but prove little.

Audits whether one implemented architectural pattern fits project needs and best practices. Use when checking pattern fitness.

Checks layer, resource ownership, and orchestration boundaries. Use when auditing architecture boundary enforcement.

Builds dependency topology, detects cycles, validates import rules, and calculates coupling metrics. Use when auditing architecture topology.

Finds architecture-level modernization opportunities: obsolete custom mechanisms, overbuilt extension points, and simplifiable architecture. Use when auditing architecture evolution.

Audits architecture config boundaries: typed settings, scattered env reads, config leakage, and layer ownership. Use for config architecture.