Claude Code Skills·Claude Skills·The open SKILL.md registry for Claude
ClaudSkillsAuthors › levnikolaevich

levnikolaevich

@levnikolaevich on GitHub →

17 Claude Code skills authored by levnikolaevich.

updated 2026-05-23 · showing 1–17 of 17 by quality score

Average Pro QualityScore: 71.4/100

For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.

Checks build, lint, type, test, and CI delivery gate failures. Use when auditing whether the project can reliably ship.
Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.
Audits assertion strength and test oracles that prove real defects. Use when finding weak tests that execute code but prove little.
Checks application security boundaries: secrets, injection, XSS, input validation, and sensitive env defaults. Use when auditing exploitable code paths.
Audits architecture config boundaries: typed settings, scattered env reads, config leakage, and layer ownership. Use for config architecture.
Checks evidence-backed duplication, over-abstraction, and unused extensibility. Use when auditing DRY/KISS/YAGNI risk.
Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview.
Audits whether one implemented architectural pattern fits project needs and best practices. Use when checking pattern fitness.
Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.
Checks runtime lifecycle and config validation: bootstrap, shutdown, probes, cleanup, env sync, and fail-fast startup. Use for runtime readiness.
Indexes and queries project research graphs backed by hex-research MCP. Use for hypotheses, goals, benchmark runs, evidence depth, derived goal metrics, lineage, generated…
Checks local maintainability hotspots: complexity, long methods, god modules, signatures, algorithms, and constants. Also flags identifier drift across API/DTO/DB layers.
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.
Checks races, deadlocks, async hazards, TOCTOU, blocking I/O, and shared resource contention. Use when auditing concurrency correctness.
Checks layer, resource ownership, and orchestration boundaries. Use when auditing architecture boundary enforcement.
Checks dependency health and generic custom utility/integration replacement opportunities. Use when auditing dependency and reuse risk.
Search all 17 skills by levnikolaevich →