protection-audit

Audit TypeScript and JavaScript protection annotations and generate reports.

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/AEtherlight-ai/lumina --skill protection-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protection-audit
Source: https://github.com/AEtherlight-ai/lumina/tree/main/.claude/skills/protection-audit
Command: npx skills add https://github.com/AEtherlight-ai/lumina --skill protection-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides comprehensive oversight of your code protection system, ensuring that critical code is consistently safeguarded. It identifies discrepancies between policy and implementation, tracks protection coverage, and automates compliance reporting, saving time and reducing risk.

Core Features & Use Cases

  • Codebase Scanning: Scans for @protected, @immutable, and @maintainable annotations across the codebase.
  • Detailed Reporting: Generates summary, detailed, and JSON reports on protection levels, files, and lock dates.
  • Consistency Verification: Checks if code annotations align with CODE_PROTECTION_POLICY.md, highlighting any inconsistencies.
  • Coverage Tracking: Measures and reports the percentage of protected files and tracks protection growth over time via Git history.
  • Use Case: Run a weekly audit to ensure all newly stabilized features are properly protected, identify any unprotected passing features, and generate a dashboard for your team to review code stability and compliance, ensuring continuous code health.

Quick Start

Audit the codebase for protection annotations and generate a summary report. Verify consistency between code protection annotations and the policy document.

Frequently Asked Questions about protection-audit

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

FAQPage Schema
How do I audit code protection annotations across my TypeScript or JavaScript project?

Code protection auditing scans your codebase for @protected, @immutable, and @maintainable annotations to identify which code is safeguarded. This Node.js CLI tool detects these annotations, excludes build and vendor directories, and generates reports showing protection status by file and level, helping you verify coverage and ensure critical code is properly marked.

Can I verify that my code annotations match a protection policy document?

Yes, this tool checks code annotations against CODE_PROTECTION_POLICY.md to highlight inconsistencies between policy requirements and actual implementation. It reports misalignments so you can align your codebase with your documented protection standards.

What types of reports can I generate from a code protection audit?

The tool produces three report formats: summary reports showing overall protection metrics, detailed reports listing protection status by file and date, and JSON reports for programmatic processing. Each format supports filtering, verification against policy, and coverage tracking options.

How do I track protection coverage growth over time in my codebase?

The audit tool measures the percentage of protected files and uses Git history to track how protection coverage evolves. This enables you to monitor compliance trends and verify that newly stabilized features are consistently receiving protection annotations.

Does this tool work with build directories and vendor code, or does it filter them out?

The tool automatically excludes build and vendor directories from scanning to focus on your source code only. This ensures reports reflect protection status in your actual project code, not dependencies or compiled output.