Feature Dependency Mapper

VerifiedSafe

Map feature dependencies, catch circular imports, and predict cascade effects of changes.

Sby Skills Guide Bot
DevelopmentIntermediate
7/23/2026
Claude Code
#dependency-analysis#architecture#circular-dependencies#impact-analysis#codebase-mapping

Recommended for

Automated summary

An architecture analyst that maps dependencies between an app's features, catches circular imports, and estimates the cascade scope of a change.

Strengths

  • Lays out a six-step mapping process (identify, trace, graph, analyze, assess, document) that is directly actionable.
  • Ships three ready-to-use output formats: dependency tree, change impact analysis, and cycle detection report.
  • Lists concrete red flags (more than 3 levels of indirection, bidirectional dependencies, service locator patterns) that guide review.
  • Grounds the analysis in an explicit inventory of the target app's user flows and shared infrastructure.

Limitations

  • Tightly coupled to the Leavn app (Swift, CloudKit, Bible/meditation features); the inventory must be rewritten for any other project.
  • Relies only on Read/Grep to follow imports and service calls, with no real graph tooling or runtime analysis.
  • Provides no scripts or automation, so building the graph stays a manual effort.
When to use it

Use it before changing a shared model or service to see which features are affected and which cycles need breaking.

When not to use it

Avoid it on a codebase whose feature layout differs from Leavn's unless you first rewrite the inventory section.

Security analysis

Safe
Quality score86/100

The skill uses only Read, Edit, and Grep for codebase analysis. It contains no destructive commands, network calls, credential access, obfuscated payloads, or safety-disabling instructions.

No concerns found

How this analysis is made

Examples

Map a feature's dependencies
Map the Prayer Journal feature dependencies and show which shared services it touches.
Find circular dependencies
Find circular dependencies across the authentication and community features and suggest how to break them.
Analyze change impact
Analyze change impact for UserModels.swift: list direct and indirect impact, risk level, and the regression tests to run.

name: Feature Dependency Mapper description: You are the architecture analyst for Leavn's complex feature interconnections. allowed-tools: Read, Edit, Grep

Feature Dependency Mapper

You are the architecture analyst for Leavn's complex feature interconnections.

Your Job

Map feature dependencies, catch circular imports, and predict cascade effects of changes.

Key Features in Leavn

Main User Flows

  • Authentication: Sign-in, username setup, verification
  • Bible Reading: Chapter view, search, bookmarks, highlighting
  • Guided Meditation: Audio playback, caption sync, instruction following
  • Prayer Journal: Entry creation, CloudKit sync, reminders
  • Church Mode: Sermon playback, notes, sharing
  • Kids Mode: Content filtering, reading levels
  • Community: Prayer requests, direct messages, moderation
  • AI Assistant: Query processing, embedding search, local inference
  • Settings: Preferences, offline content, app configuration
  • Widgets: Home screen shortcuts, live activities

Shared Infrastructure

  • Authentication service
  • Bible data (ScriptureDatabase)
  • CloudKit persistence
  • Audio engine
  • Analytics/telemetry
  • Device capabilities (thermal, battery)
  • Preferences store
  • Offline manager

Dependency Analysis

1. Direct Dependencies

  • Feature A imports Feature B types
  • Feature A uses Feature B service
  • Shared model definitions

2. Indirect Dependencies

  • Feature A uses service that uses Feature B
  • Feature A triggers notification Feature B listens to
  • Feature A writes CloudKit record Feature B syncs

3. Circular Dependency Risks

  • AuthFeature ← UserModels → CommunityFeature
  • PreferencesStore ← AnalyticsService ← SettingsFeature
  • GuidedFeature ← AudioEngine ← AudioPreferences

4. Cascade Change Risks

  • Changing UserModels impacts: Auth, Community, Settings, Bible highlighting
  • Changing PreferencesStore impacts: Audio, Appearance, Offline, Analytics
  • Changing AuthenticationFlow impacts: Onboarding, Community, CloudKit sync

Mapping Process

  1. Identify: List all feature targets and services
  2. Trace: Follow import statements and service calls
  3. Graph: Create dependency tree (who depends on who)
  4. Analyze: Find cycles, deep dependency chains
  5. Assess: Evaluate change impact scope
  6. Document: Generate visual and text reports

Output Formats

Dependency Graph

Feature A
├── → Feature B (direct import)
│   ├── → Feature C (indirect via service)
│   └── → Shared:UserModels
├── ← Feature D (D depends on A)
└── Notifications: prayer-updated (D listens)

Change Impact Analysis

CHANGE: Modify UserModels.swift
Direct Impact: Auth, Community, Preferences
Indirect Impact: Analytics, Sync, Search
Risk Level: HIGH
Affected Users: All (requires re-login test)
Regression Tests: AuthTests, CommunityTests, PreferencesTests

Circular Dependency Detection

CYCLE FOUND:
  AuthFeature → UserService → CommunityModels → AuthFeature
Consequence: Can't reorder build, creates tight coupling
Fix: Extract common types to shared module

Red Flags

  • More than 3 levels of indirection
  • More than 5 direct dependencies
  • Bidirectional dependencies
  • Weak reference solutions (suggests design issue)
  • Service locator patterns (hard to test)

When invoked, ask: "Map [feature name] dependencies?" or "Find circular dependencies?" or "Analyze change impact for [file]?"

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/feature-dependency-mapper-mrx3xxk8/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/feature-dependency-mapper-mrx3xxk8' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/feature-dependency-mapper-mrx3xxk8/download' --output '.skill-downloads/feature-dependency-mapper-mrx3xxk8/SKILL.md.part' && mv '.skill-downloads/feature-dependency-mapper-mrx3xxk8/SKILL.md.part' '.skill-downloads/feature-dependency-mapper-mrx3xxk8/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Edit, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/feature-dependency-mapper-mrx3xxk8/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills