Run Madge against a JS/TS production source tree to detect circular dependencies, find orphan modules, and visualize the module graph. Scoped to production code via `excludeRegExp` for test files. Use when a build compiles but throws `Cannot read property X of undefined` on a module that is clearly imported, or when a repo needs a CI gate that blocks new import cycles.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Madge analyzes JavaScript module graphs (AMD, CommonJS, ES6) and CSS preprocessor imports (Sass, Stylus, Less) per the Madge README. NPM deps and Node core modules are excluded by default.
Cannot read property X of undefined at runtime - likely a circular import causing partial
module init.npm install -g madge
# or per-project
npm install -D madge
Optional Graphviz for visual graphs:
| OS | Install |
|---|---|
| macOS | brew install graphviz |
| Ubuntu | apt-get install graphviz |
| Windows | choco install graphviz |
Per the Madge README.
# Single entry point
madge --circular src/index.ts
# Whole directory
madge --circular src/
Exit code: 0 if none found, 1 if any circular path exists. Use directly in CI.
# Files imported by nothing
madge --orphans src/
# Files that import nothing (terminal modules)
madge --leaves src/
Orphans are deletion candidates; verify usage outside source tree (scripts, configs, side-effect imports) before removal.
# Render full graph as SVG (requires Graphviz)
madge --image graph.svg src/
# Show what depends on a specific file
madge --depends src/config/db.ts src/
# Export raw DOT for custom rendering
madge --dot src/ > graph.gv
.madgerc in project root:
{
"fileExtensions": ["ts", "tsx", "js", "jsx"],
"excludeRegExp": [
"\\.test\\.(ts|tsx|js|jsx)$",
"\\.spec\\.(ts|tsx|js|jsx)$",
"__tests__/",
"__mocks__/",
"node_modules/",
"dist/",
"build/"
],
"tsConfig": "tsconfig.json"
}
Test files are excluded so tests can intentionally import production modules without flagging the production tree.
# GitHub Actions
- name: Block circular deps
run: npx madge --circular --extensions ts,tsx src/
- name: Detect new orphans (advisory)
run: npx madge --orphans --extensions ts,tsx src/ || true
The first step fails on any circular path; the second is informational only (orphans require human judgment - could be webpack entry, dynamic import, etc.).
| Anti-pattern | Why it fails | Fix |
|---|---|---|
Scan whole repo including node_modules/ | OOM on large workspaces | excludeRegExp: ["node_modules/"] (Step 5) - actually default behavior, but verify |
| Treat orphans as "always delete" | Webpack/Vite entry points + dynamic imports look orphaned | Manual review per orphan; use --depends to verify (Step 4) |
| Allow circular deps in non-prod with "we'll fix later" | Cycles compound; mid-project untangling is brutal | Block on first cycle (Step 6); waiver template if scope-exclusion needed |
Forget tsconfig.json for path aliases | Madge can't resolve @/foo imports; reports false positives | "tsConfig": "tsconfig.json" in .madgerc (Step 5) |
Run with default extensions (js only) for TS project | Misses 100% of TS files | fileExtensions: ["ts", "tsx", "js", "jsx"] (Step 5) |
import() calls and
require() with computed strings are not in the graph.まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Builds a CI gate that fails the build on **new** WCAG / a11y violations introduced by a PR while grandfathering pre-existing violations on a per-rule / per-page baseline. Aggregates verdicts from axe-core / pa11y / Lighthouse a11y / WAVE / IBM Equal Access scans. Use when a project has accumulated a11y debt and a strict "zero violations" gate would block every PR - the ratchet pattern lets the team ship while preventing regressions.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow skill that builds an A/B-test validity checklist from an experiment proposal, walking the canonical design-correctness gates - pre-registered OEC/power/guardrails, randomization unit + SRM check, assignment integrity, telemetry, peeking discipline, novelty/primacy, post-experiment SRM re-check - into a per-experiment checklist + sign-off form. Use when launching, auditing, or governing an experiment. For pitfall mechanics (guardrails, peeking) see experiment-results-interpreter's references; to read an already-valid result use experiment-results-interpreter; for per-SDK harness tests use experiment-sdk-testing - this gates DESIGN, not SDK code.
日本語の概要は準備中です。原文の説明を表示しています。
The single install-flow skill: the reference contract for the PWA install flow (installability gate fields, `beforeinstallprompt` handshake, per-platform paths - Android WebAPK / iOS Share menu / Firefox no-op - and the `display-mode` post-install signal, in references/install-flow-reference.md) plus the build-an-X workflow that emits the Add-to-Home-Screen suite. Walks the four-stage timeline, emitting one test per gate cell per [web.dev/articles/install-criteria][install-criteria], the deferred-prompt → `prompt()` → `userChoice` chain per [web.dev/articles/customize-install][customize-install], the iOS Safari manual-metadata branch (`apple-touch-icon`) per [web.dev/learn/pwa/installation][learn-pwa], and the post-install `(display-mode: standalone)` MQ assertion. Output: a Playwright spec with per-stage cells plus a coverage matrix. Use when a PWA's manifest, icons, or install handler change, when install conversion drops at an unknown stage, or when triaging a flaky install assertion.
日本語の概要は準備中です。原文の説明を表示しています。
Build-an-X workflow that uses an LLM to map existing tests to spec sections - given a spec doc + the test suite, the LLM identifies which tests cover which sections, surfaces uncovered sections (gap), and recommends specific tests to add. Output is a coverage matrix per spec ID. Scope is mapping tests that already exist and naming the gaps, not authoring tests for new acceptance criteria. Use when a spec doc and a test suite both exist but nobody can say which requirements are actually covered - before a release sign-off, an audit, or a decision about where to spend the next round of test effort.
日本語の概要は準備中です。原文の説明を表示しています。
Generates tests from natural-language specs (acceptance criteria, user stories, requirements) using an LLM, with confidence scoring per test case (LLM self-assessment plus heuristics: assertion quality, naming, completeness), batching uncertain cases for human review, and integration with the team's existing test framework. Use when the user asks to generate unit tests from acceptance criteria, convert user stories to test cases, automate test creation from requirements, or augment a spec-driven test suite with AI-generated stubs that are then curated before merge.
日本語の概要は準備中です。原文の説明を表示しています。
Configures Allure Report (test-runner adapter install, `allure-results` directory wiring, `categories.json` for failure classification, `history-trend.json` retention via the copy-history-between-runs pattern), runs the Allure CLI to convert `allure-results` to a static HTML site, and uploads the report as a CI artifact. Use when the team needs richer test reporting than JUnit XML - step-level attachments, per-test history, retry tracking, and severity / epic / feature labeling across framework-agnostic adapters (pytest, Jest, JUnit, TestNG, NUnit, Mocha). As a rich static HTML report generator, it is the open-source alternative to the sunset ExtentReports (JVM/.NET per-test HTML narrative); for hosted cross-run flakiness analytics rather than a static per-run report use currents-integration.
日本語の概要は準備中です。原文の説明を表示しています。