Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
configuration-inventory
description
Generate comprehensive configuration and externalized settings inventory
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, and fact-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-architecture skill. 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 what spring.jpa.open-in-view=false means for lazy loading — that belongs in data-architecture.md).
API endpoints are owned by the api-service-contracts skill. Do NOT list HTTP endpoints, controller routes, or actuator paths.
Business workflows and validation rules are owned by the business-workflows skill. Do NOT describe business processes or entity validation constraints.
Entity/domain model listings are owned by data-architecture and business-workflows. Do NOT enumerate entity names, fields, or relationships.
Execution Steps
Step 1: Generate Configuration Sources Section
Identify all configuration files and sources and produce the complete ## Configuration Sources section:
Java (Spring): application.properties, application.yml, bootstrap.properties, bootstrap.yml — note that bootstrap.* files are distinct from application.* (bootstrap configures the config server connection and runs before application context; application configures the app itself)
Identify profile activation conditions, defaults, and how profiles compose (multiple active profiles)
Step 4: Generate Properties Inventory Section
For each service/module, catalog all configuration properties and produce the complete ## Properties Inventory section:
Property keys with their default values
Which profiles/environments override each property
Data types and expected value ranges (where inferable)
Properties sourced from environment variables (${ENV_VAR}, %ENV_VAR%)
Placeholder references and property resolution chain
Do NOT include JVM startup parameters, -Xms/-Xmx heap settings, -D system properties, container memory/CPU limits, or instance counts here — those belong in the ## Startup Parameters & Resource Requirements section (Step 5).
Flag sensitive configuration entries and document the secrets provisioning workflow, and produce the complete ## Secrets & Sensitive Configuration section (including the ### Secrets Provisioning Workflow subsection):
Database passwords, API keys, connection strings with credentials
Identity/access model: managed identities, service principals, RBAC permissions (e.g., "system-assigned managed identity with get and list permissions on Key Vault")
Provisioning sequence: how secrets are set up during deployment (e.g., GitHub Actions retrieves service principal credentials → authenticates → creates MySQL secrets → binds to services)
Which services need which secrets (e.g., data services need MySQL connection strings, all services need config server credentials)
Step 8: Generate Feature Flags Section
Identify feature toggles and conditional configuration and produce the complete ## Feature Flags section:
Feature flag frameworks: Spring Feature Flags, LaunchDarkly, Unleash, .NET FeatureManagement, custom toggles
If the project has more than 100 properties, group by category (database, messaging, security, etc.) and show representative examples with counts
For multi-module projects, organize the properties inventory by module/service
Collapse repetitive property patterns (e.g., 20 similar cache TTL settings) into a summary row with count
Error Handling
Unsupported project type: Output a single line: > ERROR: Unsupported project type. This skill supports Java, .NET, JavaScript, and TypeScript projects only.
No configuration files found: Output: > ERROR: No recognized configuration files found at {workspace-path}. Verify the path is correct.
Insufficient info: Generate a best-effort inventory from available data. Add a note: > Note: Some configuration sources or properties could not be fully identified.
Success Criteria
Configuration sources table lists all discovered config files, external config repos, and secret stores
Build profiles are documented separately from runtime profiles with activation conditions and purposes
Runtime profiles are documented with config files and key overrides
Properties inventory covers all discovered properties with defaults and sources
Startup parameters and resource requirements are documented per service
Startup dependency chain shows service boot order with wait mechanisms
Secrets are identified with references (no actual values exposed) and the provisioning workflow is described
Feature flags are cataloged with defaults and controlling sources
Framework and runtime versions are documented
File saved to .github/modernize/assessment/engines/facts/configuration-inventory.md
