debug-module-resolution

Diagnose and resolve frontend module resolution failures from screenshots, logs, and project configuration evidence.

IndexedApache-2.0★ 1

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/rahul-roy-hub-debug-module-resolution

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Diagnose and resolve frontend module resolution failures from screenshots, logs, and project configuration evidence. Use when a production build cannot find a module or import.

Use cases: frontend

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/debug-module-resolution

What's inside

Skill name: debug-module-resolution
Description: Diagnose and resolve frontend module resolution failures from screenshots, logs, and project configuration evidence. Use when a production build cannot find a module or import.
License: Apache-2.0
Instructions: 33 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
troubleshooting.md · references/

SKILL.md (first lines)

# Debug Module Resolution

## Purpose

Use this skill to diagnose unresolved import and module resolution problems.

## Workflow

1. Inspect the error message.
2. Inspect import paths in the failing file.
3. Identify the unresolved module or import.
4. Verify the file path exists at the expected location.
5. Inspect path alias configuration in tsconfig or the bundler.
6. Check filename casing against the import.
7. Apply the smallest appropriate correction.
8. Run the production build.
9. Run relevant tests.

## Evidence Rules

- Prefer direct evidence from logs or screenshots.
- Distinguish observed facts from hypotheses.
- Do not claim that a cause is confirmed unless evidence supports it.
- Do not invent file names, commands, configuration values, or logs.

## Validation

- Build completes successfully.
- Relevant tests pass.
- No unresolved imports remain.
- Run the production build after the fix.

From Rahul-Roy-Hub/traceforge, Apache-2.0.

Signals

Stars: 1
Forks: 1
Open issues: 0
Last commit (this folder): Oct 4, 2026 (24 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: Apache-2.0
Repository: github.com/Rahul-Roy-Hub/traceforge
Website: traceforge-skill.vercel.app
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from Rahul-Roy-Hub

Cite this page

debug-module-resolution skill. Agent Mart. https://agentmart.dev/skills/rahul-roy-hub-debug-module-resolution (last updated 2026-10-24)