skills.rest
irvinesunday
irvinesundayCOMMUNITY
Explore all skills by this author →
GitHub

audit

Compare repository code and docs against Hali doctrine to produce severity-classified findings.

Updated Aug 27, 2026
Search Tags:#architecture#audit#governance#evidence#contracts#repo#open-issues
One-click install
npx skills add https://github.com/irvinesunday/Hali --skill audit-irvinesunday
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/irvinesunday/Hali/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/irvinesunday/Hali --skill audit-irvinesunday

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect repository reality relative to Hali doctrine, architecture documents, API contracts, and open issues, and produce evidence-backed findings classified by severity. Read-only — no implementation.

Core Features & Use Cases

  • Evidence-backed assessments that compare HEAD to doctrine, architecture, and API contracts.
  • Cross-reference open issues, migrations, and implementation status to surface drift.
  • Triage-ready reports that guide governance reviews and planning.

Quick Start

Run the audit against HEAD to generate a structured report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit a repository for architecture and governance compliance?▼

Run a read-only audit against HEAD to compare code, architecture docs, API contracts, and open issues against doctrine, producing evidence-backed findings classified by severity.

What is evidence-backed repo audit and when do I need it?▼

Evidence-backed repo audit inspects repository reality by cross-referencing implementation status with architecture documents and open issues to surface drift. You need it for governance reviews and triage planning.

Can I use this audit to check API contracts and open issues for drift?▼

Yes, the audit cross-references open issues, migrations, and API contracts against the HEAD codebase to surface drift and produce triage-ready reports for governance reviews.

Does the repo audit tool modify my code during governance checks?▼

No, the audit operates strictly read-only to ensure no implementation changes occur. It only inspects repository reality and references supporting files and lines for every finding.

How are audit findings categorized for triage decisions?▼

Audit findings are categorized by severity to guide triage decisions. The structured report cross-references open issues and migrations, ensuring every finding references supporting files and lines.

Related Skills

Explore More Software Engineering Skills→
gileckgileck

full-project-audit

Audit repository deviations from guidelines and architecture rules without code changes.

Community
Advanced
jhlee0409jhlee0409
7

afc:pr-comment

Post severity-categorized review comments to GitHub Pull Requests.

Community
Advanced
moberghrmoberghr
6

setup-audit

Audit a repository to extract architecture principles and generate .claude/references/architecture-principles.md.

Official
Intermediate
lagz0nelagz0ne
12

c3-audit

Audit C3 architecture documentation against the actual codebase.

Community
Advanced