configuration-inventory
Installation
SKILL.md
Configuration & Externalized Settings Inventory
Analyze the project to produce a comprehensive inventory of all configuration sources, build profiles, runtime profiles, externalized properties, secrets workflows, feature flags, startup dependencies, and framework versions. Save to .github/modernize/assessment/engines/facts/configuration-inventory.md.
Note: This skill produces a comprehensive reference document. For structured findings suitable for automated processing, see
fact-profile-settings,fact-environment-variables, andfact-xml-configs.
Input Parameters
workspace-path(optional): Path to the project to analyze (defaults to current directory)
Scope Boundaries — Avoid Redundancy with Other Skills
This skill is part of a set of four complementary assessment skills. To avoid content duplication across their output documents, observe these scope rules:
- Introduction: Write a 1-2 sentence intro focused on the configuration landscape (number of config sources, profiles, secrets approach). Do NOT restate the application's architecture type, business domain, or API surface.
- Database architecture details (entity models, ER diagrams, ORM mappings, caching strategy rationale, repository methods) are owned by the
data-architectureskill. In the Properties Inventory, list database-related property keys and values as raw configuration entries, but do NOT explain their behavioral implications (e.g., do not explain whatspring.jpa.open-in-view=falsemeans for lazy loading — that belongs indata-architecture.md). - API endpoints are owned by the
api-service-contractsskill. Do NOT list HTTP endpoints, controller routes, or actuator paths. - Business workflows and validation rules are owned by the
business-workflowsskill. Do NOT describe business processes or entity validation constraints. - Entity/domain model listings are owned by
data-architectureandbusiness-workflows. Do NOT enumerate entity names, fields, or relationships.