Audit forge project JSON for drift and file ownership status.
npx skills add https://github.com/reliant-labs/forge --skill audit-json
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
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.
Use forge audit --json to inspect overall_status and category results in your CI or jq-driven queries.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
reliant-labsMigrate Go projects onto Forge scaffolds with safe porting order.
githubQuery GitHub Discussions via gh CLI with optional jq filtering.
krzemienskiAggregate team validation metrics and identify projects with low posture scores.
cajiasClassify drifting fields and draft a coordinated schema relaxation plan.
