audit

Audits repositories or code changes for conformance to organizational coding and architectural standards.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill audit-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/standards/skills/audit
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill audit-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams struggle to keep codebases aligned with organizational standards for dependency injection, testing, mapping, and project structure, especially when reviewing changes across .NET, Rails, IaC, and Vue projects. ## Core Features & Use Cases - Full Repo Audit: Scans an entire repository, detects the project type, discovers existing patterns, and compares them against organizational standards. - Changes Audit: Scopes the audit to staged changes, branch diffs, or a specific GitLab MR, checking only the concerns touched by modified files. - Brownfield/Greenfield Verdicts: Applies different conformance logic depending on whether the repo has established patterns, so existing conventions are respected. - Use Case: Before merging a GitLab MR in a .NET service, run the audit with the MR flag to verify the changes use the repo's established DI container, mapping library, and testing stack rather than introducing inconsistent patterns. ## Quick Start Ask the assistant to audit the current repository against Trigent standards, or audit only staged changes by specifying the staged mode.

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 against coding standards?

Run the audit command with no arguments to scan the current working directory, or pass a path to audit a specific repo. The skill detects the project type, discovers existing patterns, and reports conformance against organizational standards.

How to audit only staged changes or a GitLab MR?

Use the --staged flag for staged changes, --branch for all changes versus the default branch, or --mr <id> to fetch the diff from a GitLab merge request. Only concerns touched by the changed files are audited.

What project types does the standards audit support?

The audit supports .NET, Rails, IaC, and Vue projects. It detects the project type automatically and loads the matching standards, scanning for concerns like DI containers, testing frameworks, mapping libraries, and state management.

Does the audit treat existing code differently from new code?

Yes. Brownfield repos with established patterns are judged primarily against repo conventions, while greenfield repos are judged directly against organizational standards. This avoids flagging intentional existing conventions as deviations.

Why does the audit report a deviation when my change matches the org standard?

In brownfield repos, a change that matches the org standard but conflicts with the repo's established pattern is flagged as a deviation because it introduces inconsistency. Repo patterns take priority for existing codebases.