protect

Annotate passing code with protection levels and update policy documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents costly regressions and ensures code stability by systematically locking down working features. It eliminates the risk of accidental changes to critical, tested code, saving hours of debugging and rework.

Core Features & Use Cases

  • Protection Levels: Apply @immutable (never change), @protected (refactor only), or @maintainable (bug fixes allowed) to code.
  • Automated Documentation: Updates CODE_PROTECTION_POLICY.md with protected files and creates bug tasks for failing features.
  • Pre-Commit Baseline: Establishes a foundation for pre-commit enforcement, ensuring policy compliance.
  • Use Case: After a major release, use this skill to mark all stable APIs and core functionalities as @immutable or @protected, ensuring future changes are carefully reviewed and approved, preventing unexpected breaks and maintaining user trust.

Quick Start

Protect the voice panel feature after reviewing manual test results. Annotate passing code with protection levels.

Frequently Asked Questions about protect

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

FAQPage Schema
How do I prevent regressions in my codebase after manual testing?

Prevent regressions by annotating passing code with protection levels (@immutable, @protected, @maintainable) based on test results. This Skill reviews manual test outcomes, assigns appropriate protection annotations to verified features, and updates policy documentation to establish a baseline that guards against accidental changes to stable code.

What are the different protection levels and when should I use each one?

Use @immutable for code that must never change, @protected for code that can only be refactored with careful review, and @maintainable for code where bug fixes are allowed. The Skill determines which level fits each feature based on test coverage and stability criteria, then documents the choice in CODE_PROTECTION_POLICY.md.

How do I set up code protection after a major release?

After release, review manual test results for all stable APIs and core functionalities. Use this Skill to annotate passing code with protection levels, which automatically updates CODE_PROTECTION_POLICY.md and creates bug tasks for any failures, establishing a pre-commit enforcement baseline.

What happens to code that fails manual tests?

Code that fails manual tests receives bug tasks created automatically by the Skill. These tasks track failures and ensure they are addressed before the code can be locked down, maintaining the integrity of your protection baseline.

Does this Skill update documentation automatically?

Yes. The Skill automatically updates CODE_PROTECTION_POLICY.md with all protected files and their assigned protection levels, eliminating manual documentation work and keeping policy records in sync with code annotations.

Related Skills