How do I install the Smoke Import skill?

Run npx skillmds@latest add jcdavis131/smoke-import in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Smoke Import safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Smoke Import?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Smoke Import free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Smoke Import?

jcdavis131 (@jcdavis131) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Smoke Import by jcdavis131 — Agent Skill

Name: Smoke Import
Author: jcdavis131

Smoke Import

Fast sanity-check that new or edited packages import cleanly, without running a full dependency sync or test suite. Use after creating/editing a Python package's __init__.py, adding a new module to a monorepo, wiring sibling packages, or before wiring a package into a router — any time you want the cheapest possible "did I wire this up" signal.

jcdavis131 Updated Sep 21, 2026

File contents

Smoke-Import

The cheapest correctness signal in a Python monorepo is "does it import". Run it before tests, before builds, before wiring into an app. It catches broken __init__.py, circular imports, missing sibling packages, and typo'd module names in under a second.

The one-liner (uv monorepo)

uv run --no-sync python -c "import sys; sys.path.insert(0, 'packages/<pkg>'); import <pkg>; print('imports ok')"

Why each flag earns its place:

--no-sync — skip dependency resolution. You're testing import wiring, not the lockfile. Saves seconds-to-minutes per check.
sys.path.insert(0, ...) — import the package straight from the tree without installing it. Lets you check a package that isn't yet a declared dependency of anything.
print('imports ok') — a positive sentinel. Silence is ambiguous; an explicit string is unambiguous success.

Multiple sibling packages at once

uv run --no-sync python -c "import sys
for p in ['packages/observability', 'packages/data-ingest']:
    sys.path.insert(0, p)
import observability, data-ingest
print('imports ok')"

Use this when a router or app depends on several new packages together — the cross-package wiring is what you're actually checking.

For non-uv projects

python -c "import sys; sys.path.insert(0, 'packages/<pkg>'); import <pkg>; print('imports ok')"

When to run

After creating a new package (packages/<pkg>/__init__.py).
After editing a package's top-level __init__.py or moving modules between packages.
Before wiring a package into an app router or service.
After a rename / move, before anything heavier.

When NOT to run

Pure data / config edits with no Python surface.
You're about to run the test suite anyway — the import will be checked there.
The package has heavy import-time side effects (DB connections, network) — smoke-import lies for those; prefer a targeted pytest --collect-only.

Limitations

Smoke-import only checks the import graph. It does NOT execute the package's logic, does NOT validate types, and does NOT catch runtime errors inside functions. Follow with a real test for anything beyond wiring.

---name: smoke-importdescription: Fast sanity-check that new or edited packages import cleanly, without running a full dependency sync or test suite. Use after creating/editing a Python package's __init__.py, adding a new module to a monorepo, wiring sibling packages, or before wiring a package into a router — any time you want the cheapest possible "did I wire this up" signal.---# Smoke-ImportThe cheapest correctness signal in a Python monorepo is "does it import". Run it before tests, before builds, before wiring into an app. It catches broken `__init__.py`, circular imports, missing sibling packages, and typo'd module names in under a second.## The one-liner (uv monorepo)```bashuv run --no-sync python -c "import sys; sys.path.insert(0, 'packages/<pkg>'); import <pkg>; print('imports ok')"```Why each flag earns its place:- `--no-sync` — skip dependency resolution. You're testing import wiring, not the lockfile. Saves seconds-to-minutes per check.- `sys.path.insert(0, ...)` — import the package straight from the tree without installing it. Lets you check a package that isn't yet a declared dependency of anything.- `print('imports ok')` — a positive sentinel. Silence is ambiguous; an explicit string is unambiguous success.## Multiple sibling packages at once```bashuv run --no-sync python -c "import sysfor p in ['packages/observability', 'packages/data-ingest']: sys.path.insert(0, p)import observability, data-ingestprint('imports ok')"```Use this when a router or app depends on several new packages together — the cross-package wiring is what you're actually checking.## For non-uv projects```bashpython -c "import sys; sys.path.insert(0, 'packages/<pkg>'); import <pkg>; print('imports ok')"```## When to run- After creating a new package (`packages/<pkg>/__init__.py`).- After editing a package's top-level `__init__.py` or moving modules between packages.- Before wiring a package into an app router or service.- After a rename / move, before anything heavier.## When NOT to run- Pure data / config edits with no Python surface.- You're about to run the test suite anyway — the import will be checked there.- The package has heavy import-time side effects (DB connections, network) — smoke-import lies for those; prefer a targeted `pytest --collect-only`.## LimitationsSmoke-import only checks the import graph. It does NOT execute the package's logic, does NOT validate types, and does NOT catch runtime errors inside functions. Follow with a real test for anything beyond wiring.

Frequently asked questions