guardrails

Detect repo rule violations with file paths and line citations.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/espensev/ai-skills --skill guardrails-espensev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guardrails
Source: https://github.com/espensev/ai-skills/tree/main/gemini-skills/skills/guardrails
Command: npx skills add https://github.com/espensev/ai-skills --skill guardrails-espensev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify repo rule violations without modifying any source files.

Core Features & Use Cases

  • Enforces contract-first, non-destructive analysis across a repository to detect governance, security, and quality violations.
  • Produces evidence-based outputs with file paths and line citations to guide remediation.
  • Suitable for large-scale, multi-team development where policy compliance must be enforced without edits.

Quick Start

Instruct the AI to scan the repository for violations without editing code.

Frequently Asked Questions about guardrails

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

FAQPage Schema
How do I scan a repository for security and compliance violations without modifying source files?

Scan a repository for security and compliance violations without editing code by instructing the AI to run a non-destructive analysis. This process detects governance and quality violations across languages while leaving all source files untouched.

Does static analysis for large codebases provide file paths and line citations for detected rule violations?

Static analysis for large codebases provides evidence-based outputs with file paths and line citations for detected rule violations. This guides remediation efforts by pinpointing exact locations of governance, security, and quality issues.

Can I use non-destructive code review for multi-team workflows across different programming languages?

Non-destructive code review supports multi-team workflows across different programming languages. It enforces contract-first analysis to detect policy compliance violations in large-scale development environments without modifying source files.

What is the 13-element Planning Contract used for in repository rule violation scanning?

The 13-element Planning Contract is enforced during repository rule violation scanning to ensure structured, non-destructive analysis. It guides the detection of governance, security, and quality violations while following global guardrails.

How do I get evidence with file paths for code review and governance violations?

Get evidence with file paths for code review and governance violations by running a non-destructive repository scan. The analysis outputs detailed citations with line numbers to guide remediation of detected security and quality issues.

What is the best way to enforce contract-first analysis across a repository without editing code?

The best way to enforce contract-first analysis without editing code is to run a non-destructive repository scan. This approach detects governance, security, and quality violations while adhering to the 13-element Planning Contract and global guardrails.