Ln 629 Lifecycle Auditor

What it does

The Ln 629 Lifecycle Auditor is a specialized worker that analyzes code changes to assess adherence to established development lifecycles and identify potential issues within an application. It checks critical areas like bootstrap, shutdown procedures, signal handling, and probes, ultimately calculating a compliance score (X/10). The skill produces a detailed markdown report outlining its findings and provides a summary back to the coordinator.

When to use it

• When ensuring proper initialization order of dependencies in your application's startup sequence.
• To verify graceful shutdown behavior, including resource cleanup before termination.
• During containerization efforts to confirm correct probe configuration and health checks.
• For auditing signal handling implementation (SIGTERM, SIGINT, SIGHUP).
• When needing a compliance score reflecting the robustness of your application's lifecycle management.

Key capabilities

• Lifecycle Audit: Checks bootstrap, shutdown, signal handling, and probes.
• Compliance Scoring: Calculates an overall compliance score (X/10).
• Bootstrap Order Verification: Analyzes initialization sequences to ensure dependencies are loaded correctly.
• Graceful Shutdown Analysis: Examines signal handlers to confirm proper resource closure.
• Resource Cleanup Validation: Checks for the release of resources like database connections and file handles during shutdown.
• Probe Configuration Check: Verifies containerized deployments have appropriate liveness/readiness probes.
• Report Generation: Creates a full markdown report using a predefined template (shared/templates/audit_worker_report_template.md).

Example prompts

• "Audit the lifecycle of my application, focusing on signal handling."
• "Check the bootstrap sequence and calculate a compliance score for this codebase."
• "Analyze resource cleanup procedures during shutdown in this project."

Tips & gotchas

• Mandatory Read: The skill requires access to shared/references/audit_worker_core_contract.md and shared/references/two_layer_detection.md for proper operation.
• Context is Key: The agent needs a context store containing the tech stack, deployment type, codebase root, and output directory.
• File Paths: The skill expects file paths to be relative to the skills repository root.