audit

Audit staged changes against ENGINEERING_PRINCIPLES.md with PASS/FAIL/WARN per principle.

7|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kkmookhey/shasta --skill audit-kkmookhey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/kkmookhey/shasta/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/kkmookhey/shasta --skill audit-kkmookhey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walk staged changes against the engineering principles checklist and report pass/fail per principle. Run before any non-trivial commit. Catches doc drift, stub functions, single-region defaults, missing framework mappings, and other regressions before they ship.

Core Features & Use Cases

  • Audits staged changes against ENGINEERING_PRINCIPLES.md and reports per-principle PASS/FAIL/WARN with file:line references.
  • Detects drift and regressions to prevent regressions before shipping.
  • Use case: pre-commit gate that enforces governance across code changes.

Quick Start

Invoke the audit before committing to gate changes against the engineering principles checklist.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I enforce engineering principles on staged git changes before a commit?

To enforce engineering principles on staged changes, audit the diff against ENGINEERING_PRINCIPLES.md. This pre-commit gate produces a PASS, FAIL, or WARN status per principle with precise file:line references to catch regressions before they ship.

What is a pre-commit code audit and how does it prevent regressions?

A pre-commit code audit walks staged changes against a governance checklist to verify compliance. It prevents regressions by detecting doc drift, stub functions, and missing framework mappings, reporting failures before the code ships.

Can I check staged diffs for compliance without an external network connection?

Yes, you can check staged diffs for compliance completely offline. The audit loads engineering principles once and runs deterministically without external network calls, ensuring reliable governance checks in any environment.

Does the pre-commit diff audit require external dependencies or framework plugins?

No, the pre-commit diff audit requires no external dependencies. It operates by analyzing the staged diff directly against your defined principles, functioning independently to enforce code review governance.

What's the best way to catch stub functions and doc drift before shipping code?

The best way to catch stub functions and doc drift is running a staged diff audit against your engineering principles. This pre-commit check identifies single-region defaults and drift with exact file:line references.

Why would a pre-commit governance check return a WARN status instead of FAIL?

A pre-commit governance check returns a WARN status when a staged change partially violates an engineering principle but does not fully block the commit. It flags potential drift or missing mappings with file:line references for review.