skill-dev

Detect cross-module coupling, N+1 queries, dead exports, and antipatterns with file-path findings.

3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/marcoguillermaz/claude-dev-kit --skill skill-dev-marcoguillermaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-dev
Source: https://github.com/marcoguillermaz/claude-dev-kit/tree/main/packages/cli/templates/tier-s/.claude/skills/skill-dev
Command: npx skills add https://github.com/marcoguillermaz/claude-dev-kit --skill skill-dev-marcoguillermaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers and teams need a rigorous, repeatable way to assess code quality across a codebase and surface technical debt, including cross-module coupling, N+1 queries, dead exports, antipatterns, and overly large components.

Core Features & Use Cases

  • Cross-module coupling detection to surface unwanted dependencies across feature boundaries.
  • N+1 query detection and dead exports to improve maintainability and performance.
  • Antipattern detection and oversized components with alignment to a refactoring backlog.
  • Structured findings anchored to concrete file paths to support reviews and remediation planning.

Quick Start

Audit your repository to produce a backlog-ready report of code-quality findings without modifying source code.

Frequently Asked Questions about skill-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit code quality and detect technical debt across a large codebase?

Code-quality auditing detects cross-module coupling, N+1 queries, dead exports, and antipatterns by anchoring each finding to concrete file paths. This process produces a backlog-ready report without modifying source code.

What is the best way to detect N+1 queries and dead exports in my project?

Detecting N+1 queries and dead exports requires static analysis that targets mid-to-large projects across languages and frameworks. It enforces an audit-only mode with a configurable lint command to surface these maintainability and performance issues.

Does this code-review auditing approach work across different programming languages and frameworks?

Yes, this code-review auditing approach works across different languages and frameworks. It targets mid-to-large projects to identify cross-module coupling and oversized components, generating structured findings that support reviews and remediation planning.

How do I generate a refactoring backlog from static analysis findings?

To generate a refactoring backlog from static analysis findings, run an audit-only lint command that detects antipatterns and oversized components. It produces a structured report aligning each finding with concrete file paths to support backlog tracking and remediation planning.

Can I identify cross-module coupling without modifying my existing source code?

Yes, you can identify cross-module coupling without modifying existing source code. The audit enforces an audit-only mode with a configurable lint command, preserving existing behavior while surfacing unwanted dependencies across feature boundaries in a structured report.