repo-compliance-audit

Audit repository compliance and generate markdown reports with Python scripts.

50|3|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/okwinds/miscellany --skill repo-compliance-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-compliance-audit
Source: https://github.com/okwinds/miscellany/tree/main/agent/skills/repo-compliance-audit
Command: npx skills add https://github.com/okwinds/miscellany --skill repo-compliance-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates repository compliance auditing to produce verifiable reports.

Core Features & Use Cases

  • Audit any codebase to generate a human-readable report and machine-readable findings, covering essentials like AGENTS.md, DOCS_INDEX.md, SPEC/Spec entries, worklogs, and environment files.
  • Remediation workflow to select findings for safe, targeted fixes without altering core business logic; outputs a remediation report and status.
  • Integrates a two-stage process (Audit → Remediation) and can redact sensitive data when sharing outputs.

Quick Start

From the skill directory run audit: python3 scripts/audit_repo.py --repo . --out /tmp/repo-compliance-audit Then apply selected fixes: python3 scripts/remediate_repo.py --repo . --findings /tmp/repo-compliance-audit/findings.json --select DOCS_INDEX_MISSING,ENV_EXAMPLE_MISSING

Frequently Asked Questions about repo-compliance-audit

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

FAQPage Schema
How do I automate repository compliance auditing for required governance files?

Automate repository compliance auditing by running Python scripts to scan a codebase for required files like AGENTS.md, DOCS_INDEX.md, specs, worklogs, and .env examples, generating verifiable markdown reports and machine-readable findings.

What is the best way to fix missing compliance files found during a git repository audit?

Fix missing compliance files found during a git repository audit by applying a two-stage remediation workflow that selects specific findings for safe, targeted fixes without altering core business logic, outputting a remediation report and status.

Can I redact sensitive data when sharing repository audit findings?

Yes, you can redact sensitive data when sharing repository audit findings. The auditing process supports optional redaction to ensure safe sharing of both human-readable markdown reports and machine-readable findings outputs.

Does the repository audit script require external dependencies to run?

No, the repository audit script does not require external dependencies. It produces verifiable compliance reports using Python standard library scripts, meaning no additional package installation is needed before executing the audit or remediation workflows.

How do I select specific findings to remediate after a repository audit?

Select specific findings to remediate after a repository audit by passing the findings.json file to the remediation script with the desired finding codes, such as DOCS_INDEX_MISSING or ENV_EXAMPLE_MISSING, to apply targeted fixes.