audit-json

Audit forge project JSON for drift and file ownership status.

4|1|Updated Apr 12, 2026

Search Tags:#drift detection #json #forge #ci gating #codegen audit #jq queries #project shape

Ready to run

npx skills add https://github.com/reliant-labs/forge --skill audit-json

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-json
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/audit-json
Command: npx skills add https://github.com/reliant-labs/forge --skill audit-json

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forge users need a reliable, machine-readable way to detect drift, version mismatches, and unhealthy project shape so CI and dashboards can gate changes without brittle log parsing.

Core Features & Use Cases

Read stable audit and map JSON: use forge audit --json for per-run health rollups and forge map --json for an annotated file ownership tree.
Support CI gates and dashboards: fail builds deterministically by checking overall_status and per-category status, while still retaining structured detail for reports.
Enable sub-agent and LLM workflows: let agents query project shape and codegen drift (including hand-edited generated files) before deciding whether to regenerate or scaffold.

Quick Start

Use forge audit --json to inspect overall_status and category results in your CI or jq-driven queries.

Frequently Asked Questions about audit-json

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

FAQPage Schema

How do I detect project drift in CI without parsing logs?▼

You can detect project drift deterministically in CI by running forge audit --json to output a stable JSON contract with overall_status and per-category results, allowing pipelines to gate builds without brittle log parsing.

What is the JSON structure for forge audit and map outputs?▼

The forge audit and map JSON structure is an additive contract featuring overall_status, per-category status, summary, and details, plus a map tree with file ownership and drift flags suitable for long-term jq filtering compatibility.

How do I check file ownership and codegen drift in a forge project?▼

To check file ownership and codegen drift, run forge map --json to generate an annotated file tree map that highlights ownership and flags hand-edited generated files for sub-agent workflows.

Can I use jq to filter forge audit results for dashboard reporting?▼

Yes, you can use jq queries to filter the machine-readable forge audit JSON output, extracting specific per-category status and details to populate automated quality gates and dashboard reports.

How do LLM sub-agents query project shape before regenerating code?▼

LLM sub-agents query project shape by reading the stable forge audit and map JSON outputs, analyzing the ownership tree and drift flags to decide whether to regenerate or scaffold files.

Does forge audit --json support long-term consumer compatibility?▼

Forge audit --json supports long-term consumer compatibility by providing a stable, additive JSON contract that preserves existing fields while appending new status and details for reliable CI gating.