advanced-lokstra-validate-consistency

Detect circular dependencies, misconfigurations, and annotation issues in Lokstra applications.

8|1|Updated Jun 21, 2025
One-click install
npx skills add https://github.com/primadi/lokstra --skill advanced-lokstra-validate-consistency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advanced-lokstra-validate-consistency
Source: https://github.com/primadi/lokstra/tree/main/.github/skills/advanced-lokstra-validate-consistency
Command: npx skills add https://github.com/primadi/lokstra --skill advanced-lokstra-validate-consistency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gopkg.in/yaml.v3, github.com/lib/pq, and includes scripts (resource) components.

What problem does it solve?

This skill identifies and reports inconsistencies in Lokstra applications, including circular dependencies, misconfigurations, and annotation issues that could break deployments.

Core Features & Use Cases

  • Static analysis: detect circular dependencies and invalid annotations across modules.
  • Config and migrations validation: ensure config files and migrations align with deployment expectations.
  • Pre-deployment checks: validate service registrations and DI wiring to prevent runtime failures.

Quick Start

Run the pre-deploy validation workflow to identify issues early. For example, run: bash scripts/pre_deploy_check.sh

Frequently Asked Questions about advanced-lokstra-validate-consistency

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

FAQPage Schema
How do I validate application consistency before a CI/CD deployment?

To validate application consistency before a CI/CD deployment, run the pre_deploy_check.sh script to perform static analysis, config validation, and database schema checks. This detects circular dependencies, misconfigurations, and annotation issues before they break deployment.

What is static analysis for circular dependencies and annotation issues?

Static analysis for circular dependencies and annotation issues scans modules to detect invalid configurations and wiring problems. It enforces code completeness and checks that config and migration files align with deployment expectations.

How do I check database schema and migrations for deployment readiness?

You check database schema and migrations for deployment readiness by running validation that verifies migration files exist and align with the database schema. This ensures the environment is prepared for runtime validation.

Does this validation tool work with YAML configs and PostgreSQL databases?

Yes, this validation tool works with YAML configs and PostgreSQL databases by parsing configuration files and querying database schemas. It ensures that both static config files and runtime database states are consistent for safe deployment.

What are the limitations of pre-deployment consistency checks?

The limitation of pre-deployment consistency checks is that they require code to be complete through Phase 1-2, with config and migration files already present. It cannot validate incomplete code or missing migration files in the environment.