audit

Audit repository codebase and spec conformance against engineering standards.

2|Updated May 19, 2026
One-click install
npx skills add https://github.com/element22llc/e22-plugins --skill audit-element22llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/element22llc/e22-plugins/tree/main/plugins/steer/skills/audit
Command: npx skills add https://github.com/element22llc/e22-plugins --skill audit-element22llc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of auditing a repository's code health and spec conformance, identifying potential issues and ensuring standards adherence without modifying code or spec directly.

Core Features & Use Cases

  • Code Health Audit: Sweeps the entire codebase against engineering standards, ranking findings by leverage.
  • Spec Conformance: Compares the as-built spec against the intended spec, surfacing drift.
  • Read-Only: Proposes changes and files issues but never edits code or spec.
  • Use Case: Before a release or milestone, use this Skill to perform a comprehensive audit of your repository to ensure all standards are met.

Quick Start

Run the audit skill on your repository with the 'code' mode to perform a health check against the standards.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit my repository for code health and spec conformance?

To audit repository code health and spec conformance, run the skill in 'code' mode to sweep the codebase against engineering standards, identify deviations, and rank findings by leverage without modifying files.

What is spec drift and how do I detect it in my codebase?

Spec drift occurs when the as-built spec diverges from the intended spec. You can detect spec drift by comparing the as-built spec against the intended spec to surface deviations and ensure standard compliance.

Do I need Git and Bash to perform a codebase audit?

Yes, you need Bash, Git, and GitHub Issue Tracker access to perform a codebase audit, as the skill requires these dependencies to automate repository sweeps, compare specs, and file issues.

Can this repository audit propose changes without modifying my code?

Yes, the repository audit operates in a read-only mode, meaning it proposes changes and files issues in the GitHub Issue Tracker but never edits your code or spec directly.

When should I run a code health audit on my repository?

You should run a code health audit before a release or milestone to perform a comprehensive sweep of your repository, ensuring all engineering standards are met and identifying potential improvements.

What is the best way to ensure engineering standards adherence before a release?

The best way to ensure engineering standards adherence before a release is to automate a full codebase audit, which ranks findings by leverage and surfaces spec drift without directly modifying code.