revealui-safety

Enforce safety guardrails on RevealUI monorepo code changes.

4|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/RevealUIStudio/revealui --skill revealui-safety
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revealui-safety
Source: https://github.com/RevealUIStudio/revealui/tree/main/.agents/skills/revealui-safety
Command: npx skills add https://github.com/RevealUIStudio/revealui --skill revealui-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide safety guardrails for code changes in the RevealUI monorepo to prevent credential exposure, enforce import boundaries, ensure code quality, and verify work before completion.

Core Features & Use Cases

  • Protected Files: Prohibits editing of sensitive files like .env*, lock files, and certain database schema files without proper planning.
  • Protected Paths: Prevents edits in system directories and credential stores.
  • Import Boundaries: Restricts allowed module usage across repository boundaries to minimize risk.
  • Code Quality: Enforces no use of any, avoids console in production, forbids hardcoded secrets, and recommends secure randomness.
  • Static Analysis & Governance: Prefers AST-based checks over regex and implements validation steps after edits and before marking work done.
  • Known Limitations: Documents advisory nature and when to explicitly invoke safety checks.

Quick Start

Follow the safety rules and enforce guardrails on the next code change before merging.

Frequently Asked Questions about revealui-safety

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

FAQPage Schema
How do I prevent hardcoded secrets and credential leakage in a monorepo?

Enforce import boundaries in a monorepo by restricting allowed module usage across repository boundaries. This minimizes risk by ensuring code only imports from approved areas during editing and refactoring.

What static analysis checks are needed for secure code review guardrails?

Protected files and paths prevent edits to sensitive files like .env*, lock files, and database schema files, along with system directories and credential stores. This ensures sensitive configuration remains untouched during routine refactoring.

How do I enforce code quality rules before marking a code task done?

Enforce code quality before completion by implementing validation steps after edits. Apply governance checks to ensure no any types, no console in production, and no hardcoded secrets, verifying work is compliant and auditable before merging.

What are the limitations of automated safety guardrails for code changes?

Automated safety guardrails have an advisory nature and require explicit invocation in certain contexts. Known limitations mean you must manually trigger safety checks when specific boundary conditions are not automatically detected.