audit

Audit Granit .NET modules for framework convention compliance.

18|4|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/granit-fx/granit-dotnet --skill audit-granit-fx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/granit-fx/granit-dotnet/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/granit-fx/granit-dotnet --skill audit-granit-fx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires granit-tools, roslyn-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework audit for Granit .NET modules, ensuring they adhere to the established conventions, architecture rules, and CLAUDE.md standards.

Core Features & Use Cases

  • Framework Convention Compliance: Checks module anatomy, DDD, naming, OpenAPI, persistence, validation, events, metrics, localization, documentation, and cross-cutting concerns.
  • Invoke for Convention Compliance: Use this Skill before merging or during tech-debt sprints to verify convention compliance.
  • Audit Modes: Offers full audit, module audit, and PR audit modes to target specific scenarios.

Quick Start

Run the audit skill with the command: /audit

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit .NET modules for DDD and OpenAPI convention compliance?

A convention compliance audit checks module anatomy, DDD, OpenAPI, persistence, and cross-cutting concerns against framework standards, identifying violations by severity and optionally fixing them using Roslyn type inspection.

How do I check Granit .NET code against CLAUDE.md standards before merging?

You can verify Granit .NET code against CLAUDE.md standards before merging by running a PR audit, which targets specific scenarios to verify convention compliance and identify architecture violations by severity.

Do I need Roslyn MCP tools to inspect .NET module architecture rules?

Yes, Roslyn MCP tools are required for type inspection to perform detailed .NET module audits, as they collect structural context and apply checklist rules to identify convention violations.

What's the best way to fix DDD and naming convention violations in .NET modules?

The best way to fix DDD and naming convention violations in .NET modules is to run a framework audit that identifies violations by severity and optionally applies fixes based on collected structural and convention context.

Can I run a full architecture audit during a tech-debt sprint?

Yes, you can run a full architecture audit during a tech-debt sprint using the full audit mode, which comprehensively checks module anatomy, validation, events, metrics, and localization against framework conventions.

What limitations exist when auditing .NET persistence and validation conventions?

Auditing .NET persistence and validation conventions requires granit-tools and Roslyn MCP tools for type inspection, meaning the audit process is limited to environments where these dependencies are properly configured and available.