scafforge-audit

Diagnose repository-health issues and output a four-report diagnosis pack.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/merceralex397-collab/Scafforge --skill scafforge-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scafforge-audit
Source: https://github.com/merceralex397-collab/Scafforge/tree/main/skills/scafforge-audit
Command: npx skills add https://github.com/merceralex397-collab/Scafforge --skill scafforge-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

Run Scafforge's host-side diagnosis flow for an existing repository. Use when a repo needs workflow diagnosis, contract verification, professional codebase review, or a four-report diagnosis pack with evidence-backed ticket recommendations and no repair edits.

Frequently Asked Questions about scafforge-audit

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

FAQPage Schema
What is non-mutating repository health diagnosis and how does it work?

Non-mutating repository health diagnosis analyzes a repo's workflow, specs, and design documents to validate contract compliance and output evidence-backed ticket recommendations without modifying any source files or repository state.

How do I audit a repository for workflow and contract verification issues?

Run a host-side diagnosis flow against the subject repository to audit workflow issues and verify contracts. The process applies Scafforge contract rules to supporting artifacts and logs, producing a four-report diagnosis pack with traceable findings and safe repair guidance.

Can I perform a codebase review without making repair edits to the repository?

Yes, this non-mutating host diagnosis flow performs a professional codebase review and outputs evidence-backed ticket recommendations with safe repair guidance, ensuring the repository remains completely unmodified during the audit process.

What does a four-report diagnosis pack contain for repository analysis?

A four-report diagnosis pack contains evidence-backed ticket recommendations derived from analyzing repository specs, plans, notes, and design documents. It ensures traceable findings by leveraging Scafforge contract rules and supporting artifact logs.

When do I need a diagnosis pack with evidence-backed ticket recommendations?

You need a diagnosis pack when a repository containing specs, plans, notes, or design documents requires workflow diagnosis, contract verification, or professional codebase review with traceable findings and safe repair guidance.

What are the limitations of non-mutating repository audit approaches?

Non-mutating repository audits are limited to read-only diagnosis and evidence-backed ticket recommendations; they do not execute repair edits or directly mutate the repository, meaning all safe repair guidance requires separate manual implementation.