workspace-audit

Scan repositories for Claude hygiene, dependency, and source quality violations.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/ManfronEnrico/thesis-manifold --skill workspace-audit-manfronenrico
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-audit
Source: https://github.com/ManfronEnrico/thesis-manifold/tree/main/.claude/skills/workspace-audit
Command: npx skills add https://github.com/ManfronEnrico/thesis-manifold --skill workspace-audit-manfronenrico

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Read-only repository health auditor. Scans a repository against Claude hygiene, dependency, and source quality violations.

Core Features & Use Cases

  • Validate repository health by surfacing hygiene, dependency, and code-quality issues before merges.
  • Export findings as JSON for CI integration or downstream tooling.
  • Provide actionable guidance to fix detected violations and gate decisions.

Quick Start

Run the audit from the repository root to generate a findings report and optionally output JSON.

Frequently Asked Questions about workspace-audit

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

FAQPage Schema
How do I audit my repository for security and hygiene issues in CI?

You can audit repository security and hygiene by scanning CLAUDE.md, skill metadata, and dependency configs against 18 rules. It returns structured JSON with high, medium, and low findings alongside a gate status to block or allow CI merges.

What does a repository hygiene check include for Claude configurations?

A repository hygiene check scans CLAUDE.md and skill metadata to surface hygiene, dependency, and source quality violations. It evaluates 18 specific rules to provide actionable guidance for fixing detected violations before code merges.

Can I generate a JSON report of dependency and code quality findings for downstream tooling?

Yes, you can export audit findings as JSON for downstream tooling. The structured output includes severity levels and gate status, making it straightforward to parse repository health results in CI pipelines or external dashboards.

Does the repository audit work across submodules or only the root directory?

The repository audit supports an optional path argument to run across root and submodules. This allows you to comprehensively scan dependency configs and source quality rules throughout nested repository structures.

How do I use audit findings to gate merges in my CI pipeline?

You can gate merges by parsing the structured JSON output which includes a gate status based on the high, medium, and low findings. This enables automated CI decisions to block merges when repository hygiene or security violations are detected.