skills.rest
victorp1leon
victorp1leonCOMMUNITY
Explore all skills by this author →
GitHub

repo-audit-safety

Audit Git repositories for governance gaps, safety risks, and non-compliant configurations.

Updated Mar 6, 2026
Search Tags:#documentation#audit#remediation#safety#governance#evidence
One-click install
npx skills add https://github.com/victorp1leon/openclaw-bakery --skill repo-audit-safety
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-audit-safety
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/.codex/skills/repo-audit-safety
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill repo-audit-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenClaw Bakery teams need a safety-first, evidence-based repository audit process that surfaces governance gaps, safety risks, and non-compliant configurations before changes are made.

Core Features & Use Cases

  • Non-mutating audits that map current health and compliance without altering code or documentation.
  • Evidence-backed findings with prioritized remediation suggestions and clear risk signals.
  • Guardrails and approval gates to prevent unauthorized changes and ensure documented decisions.
  • Use case: Run audits across the entire repo or targeted paths and produce a plan for safe improvements.

Quick Start

Run a non-mutating repository audit to generate evidence-based findings and low-risk remediation suggestions.

Frequently Asked Questions about repo-audit-safety

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

FAQPage Schema
How do I audit a Git repository for safety risks and governance gaps?▼

Run a non-mutating repository audit that analyzes project context from AGENTS.md and documentation plans to surface evidence-backed findings on governance gaps and safety risks without altering code.

What is a non-mutating repository audit and when do I need one?▼

A non-mutating repository audit maps current project health and compliance status without altering code. You need this process to identify safety risks and non-compliant configurations before authorizing changes.

Can I target a specific directory path instead of auditing the entire project?▼

Yes, you can apply the repository audit to specified paths rather than the entire project. This scopes governance and safety checks to targeted directories while still producing evidence-backed findings and bounded remediations.

Does the audit process require approval gates before suggesting remediations?▼

Yes, the audit process uses explicit approval gates to prevent unauthorized changes. It outputs bounded remediation suggestions with clear risk signals, ensuring documented decisions and safe improvements.

What context files are required to perform a governance and compliance audit?▼

The audit requires loading project context from AGENTS.md, .codex/rules, and documentation plans. These files provide the governance and safety rules needed to generate evidence-backed findings.

Related Skills

Explore More Legal & Compliance Skills→
samjhechtsamjhecht
4

initialize-governance

Generate Constitution, Roadmap, and process documentation templates for project governance.

Community
Advanced
valithedgevalithedge

security-hardening

Audit AMS Dispatcher security configurations and deliver remediation guidance.

Community
Advanced
kkmookheykkmookhey
7

evidence

Collects and stores timestamped compliance evidence snapshots for audits in cloud environments.

Community
Intermediate
issdandavisissdandavis
6

scbe-copilot

Review the SCBE-AETHERMOORE codebase for defects and governance risks.

Community
Advanced