ln-629-lifecycle-auditor

Application lifecycle audit worker (L3). Checks bootstrap initialization order, graceful shutdown, resource cleanup, signal handling, liveness/readiness probes. Returns findings with severity, location, effort, recommendations.

⭐25stars🔀7forks📁View on GitHub🕐Updated Jan 10, 2026

When & Why to Use This Skill

The Lifecycle Auditor is a specialized L3 worker designed to automate the auditing of application lifecycle management and entry points. It evaluates critical operational patterns including bootstrap initialization sequences, graceful shutdown procedures, resource cleanup, signal handling, and Kubernetes-ready liveness/readiness probes. By providing detailed findings with severity levels, effort estimates, and actionable recommendations, it ensures applications are resilient, production-ready, and compliant with SRE (Site Reliability Engineering) best practices.

Use Cases

  • Production Readiness Review: Automatically audit a new service before deployment to ensure it handles SIGTERM signals and includes health check endpoints for container orchestration.
  • Resource Leak Prevention: Identify missing cleanup logic in shutdown handlers to prevent database connection leaks and file handle exhaustion during service restarts.
  • Startup Sequence Debugging: Analyze the bootstrap phase to detect incorrect initialization orders that could lead to race conditions or startup failures.
  • SRE Compliance Auditing: Generate standardized reliability scores across multiple microservices to maintain high engineering standards and operational consistency across a distributed architecture.
nameln-629-lifecycle-auditor
descriptionApplication lifecycle audit worker (L3). Checks bootstrap initialization order, graceful shutdown, resource cleanup, signal handling, liveness/readiness probes. Returns findings with severity, location, effort, recommendations.
allowed-toolsRead, Grep, Glob, Bash

Lifecycle Auditor (L3 Worker)

Specialized worker auditing application lifecycle and entry points.

Purpose & Scope

  • Worker in ln-620 coordinator pipeline
  • Audit lifecycle (Category 12: Medium Priority)
  • Check bootstrap, shutdown, signal handling, probes
  • Calculate compliance score (X/10)

Inputs (from Coordinator)

Receives contextStore with tech stack, deployment type, codebase root.

Workflow

  1. Parse context
  2. Check lifecycle patterns
  3. Collect findings
  4. Calculate score
  5. Return JSON

Audit Rules

1. Bootstrap Initialization Order

Detection:

  • Check main/index file for initialization sequence
  • Verify dependencies loaded before usage (DB before routes)

Severity:

  • HIGH: Incorrect order causes startup failures

Recommendation: Initialize in correct order: config → DB → routes → server

Effort: M (refactor startup)

2. Graceful Shutdown

Detection:

  • Grep for SIGTERM, SIGINT handlers
  • Check process.on('SIGTERM') (Node.js)
  • Check signal.Notify (Go)

Severity:

  • HIGH: No shutdown handler (abrupt termination)

Recommendation: Add SIGTERM handler, close connections gracefully

Effort: M (add shutdown logic)

3. Resource Cleanup on Exit

Detection:

  • Check if DB connections closed on shutdown
  • Verify file handles released
  • Check worker threads stopped

Severity:

  • MEDIUM: Resource leaks on shutdown

Recommendation: Close all resources in shutdown handler

Effort: S-M (add cleanup calls)

4. Signal Handling

Detection:

  • Check handlers for SIGTERM, SIGINT, SIGHUP
  • Verify proper signal propagation to child processes

Severity:

  • MEDIUM: Missing signal handlers

Recommendation: Handle all standard signals

Effort: S (add signal handlers)

5. Liveness/Readiness Probes

Detection (for containerized apps):

  • Check for /live, /ready endpoints
  • Verify Kubernetes probe configuration

Severity:

  • MEDIUM: No probes (Kubernetes can't detect health)

Recommendation: Add /live (is running) and /ready (ready for traffic)

Effort: S (add endpoints)

Scoring Algorithm

penalty = (high * 1.0) + (medium * 0.5) + (low * 0.2)
score = max(0, 10 - penalty)

Output Format

{
  "category": "Lifecycle",
  "score": 7,
  "total_issues": 4,
  "high": 1,
  "medium": 3,
  "low": 0,
  "findings": [
    {
      "severity": "HIGH",
      "location": "src/index.ts:1-50",
      "issue": "No SIGTERM handler for graceful shutdown",
      "principle": "Graceful Shutdown / Resource Management",
      "recommendation": "Add SIGTERM handler to close DB connections and server gracefully",
      "effort": "M"
    }
  ]
}

Version: 3.0.0 Last Updated: 2025-12-23