module-dependency-audit

Verify .imodspec dependencies match actual code and template references in Intent Architect modules.

23|10|Updated Aug 31, 2017
One-click install
npx skills add https://github.com/IntentArchitect/Intent.Modules --skill module-dependency-audit-intentarchitect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: module-dependency-audit
Source: https://github.com/IntentArchitect/Intent.Modules/tree/main/Tests/ModuleBuilderSkills/.opencode/skills/module-dependency-audit
Command: npx skills add https://github.com/IntentArchitect/Intent.Modules --skill module-dependency-audit-intentarchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A module can compile and pass its Software Factory run while missing dependencies in its .imodspec manifest, causing failures only when consumers install it. This Skill audits the generated dependency list against what the module's code and templates actually reference, catching install-time failures before release. ## Core Features & Use Cases - Reference Collection: Gathers the module's real references from .csproj PackageReference entries, Intent.* namespaces imported by templates and factory extensions, and designer metadata reads. - Manifest Comparison: Compares the generated <dependencies> section of the .imodspec against the referenced set, flagging referenced-but-undeclared entries while leaving legitimate transitive dependencies alone. - Source-First Fixing: Corrects missing dependencies at the source (installing the module or adding the PackageReference) and regenerates, with hand-added dependency entries as a supported fallback since they survive regeneration. - Use Case: Before closing out a module change, run the audit to confirm every Intent module your templates reference is declared in the manifest, so downstream consumers do not hit missing-type errors at install time. ## Quick Start Audit this module's .imodspec dependencies against its actual code and template references and report any referenced but undeclared dependencies.

Frequently Asked Questions about module-dependency-audit

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

FAQPage Schema
How do I verify .imodspec dependencies in an Intent Architect module?▼

Collect the module's actual references from its .csproj PackageReference entries, the Intent.* namespaces its templates and factory extensions import, and designer metadata reads. Compare that set against the generated <dependencies> section and resolve anything referenced but not declared.

Why does my module compile but fail when consumers install it?▼

The Software Factory infers dependencies from installed modules rather than actual code references, so a type reached through a transitively available assembly compiles fine but is never declared. At install time in a consumer's application, that missing dependency surfaces as a failure.

Can I hand-edit dependencies in the .imodspec file?▼

Yes, dependency entries are added if absent and never pruned, so a hand-added entry survives regeneration. Use this only when fixing the source reference and regenerating still does not produce the entry, and match the Intent module id exactly rather than the NuGet package id.

Should I remove dependencies that look unused in the manifest?▼

No. An entry that looks surplus is usually a legitimate transitive or event-raised dependency. Leave it unless you can demonstrate that nothing in the module actually needs it.

Can I edit modules.config to fix dependency problems?▼

No. modules.config is never hand-edited because it records what is installed, and a bad edit corrupts the application's module state. Change it only by installing or updating modules through Intent Architect.