skills.rest
ze-software
ze-softwareOFFICIAL
Explore all skills by this author →
GitHub

ze-audit

Audit Ze specs against the codebase and report Done/Partial/Missing statuses with file:line evidence.

50|2|Updated Mar 27, 2026
Search Tags:#codebase#audit#reporting#evidence#spec#ze
One-click install
npx skills add https://github.com/ze-software/ze --skill ze-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ze-audit
Source: https://github.com/ze-software/ze/tree/main/.codex/skills/ze-audit
Command: npx skills add https://github.com/ze-software/ze --skill ze-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill performs a repo-specific audit for the Ze repository. It reads the current spec, compares it against the codebase, and reports what is already done, partially complete, or missing without making changes.

Core Features & Use Cases

  • Repo-spec alignment checks: verify that plan items align with code, tests, and documentation.
  • Evidence-backed reporting: produce a status table with precise references to files and lines.
  • Read-only auditing: no code changes are made during the audit.
  • Use case: validate an upcoming feature spec against the repository to identify gaps before implementation.

Quick Start

Run the audit workflow to read tmp/session/selected-spec and generate a compliance report against the plan and codebase.

Frequently Asked Questions about ze-audit

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

FAQPage Schema
How do I check if my codebase aligns with project specifications?▼

To check codebase alignment with specifications, you can run an audit workflow that reads your selected spec file and compares planned requirements against the actual code, tests, and wiring to report gaps.

What is the best way to verify feature spec compliance before implementation?▼

The best way to verify feature spec compliance is to perform a read-only audit that compares your upcoming feature spec against the repository, identifying what is done, partial, or missing to guide implementation.

How do I generate an evidence-backed compliance report for my codebase?▼

You generate an evidence-backed compliance report by running an audit workflow that validates plans, file lists, and wiring checks against the codebase, producing a status table with precise file and line references.

Does the spec audit process modify my repository files?▼

No, the spec audit process is entirely read-only and makes no code changes to your repository during the validation of specs, plans, and wiring checks against the actual codebase.

What does a Done, Partial, or Missing status mean in a spec audit report?▼

In a spec audit report, Done, Partial, or Missing statuses indicate the current implementation level of planned requirements, providing precise evidence references to help guide upcoming implementations.

Related Skills

Explore More Software Engineering Skills→
ze-softwareze-software
50

ze-implement

Automate phased spec implementation with tests and status tracking in the Ze repository.

Official
Advanced
joshsmithxrmjoshsmithxrm
5

spec-audit

Audit specifications against codebases to identify drift, gaps, and undocumented behavior.

Community
Advanced
devstefanchodevstefancho
11

spec-manager

Organize spec files under specs/{scope}/{work-name}.md with XML tag enforcement.

Community
Advanced
vinaykumarvkvinaykumarvk
1

coding-standards-review

Scan codebases for security flaws, quality issues, and accessibility violations.

Community
Advanced