eightforge-audit-reviewer

Reviews audit logs, provenance trails, and compliance history for EightForge code changes.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-audit-reviewer-ericanalysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eightforge-audit-reviewer
Source: https://github.com/EricAnalysis/eightforge-os/tree/main/.cursor/skills/eightforge-audit-reviewer
Command: npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-audit-reviewer-ericanalysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changes to audit logging, activity tracking, and provenance systems can silently break compliance guarantees, lose history, or blur the line between current state and historical events. This Skill provides a structured review process that catches broken event contracts, missing provenance, and immutability violations before they ship. ## Core Features & Use Cases - Audit Contract Review: Classifies every mutation's history obligation as transactionally required, durable/retriable, or best-effort, and verifies failure handling matches that severity. - Provenance and Immutability Checks: Validates source-to-execution lineage, immutable run history, supersession, override, and correction trails without rewriting the past. - Authority Classification: Labels findings as production authority, compatibility, shadow, design target, or superseded to prevent shadow or design artifacts from masquerading as live truth. - Use Case: When a pull request modifies activity_events writes or adds a new decision override flow, invoke this Skill to verify the event contract, identity fields, and rollback behavior produce a complete, reconstructable audit trail. ## Quick Start Review this pull request touching activity_events and decision provenance for audit contract violations and missing history.

Frequently Asked Questions about eightforge-audit-reviewer

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

FAQPage Schema
How do I review changes to audit logs and activity_events tables?▼

Use this review Skill to check each material mutation against its declared audit contract. It verifies whether history is transactionally required, durable/retriable, or best-effort, and confirms failure handling, identity fields, and before/after semantics match that classification.

How to verify provenance and decision lineage in a code review?▼

The reviewer traces source-to-observation-to-fact-to-decision-to-execution lineage and checks that supersession, override, and correction history is preserved without rewriting the past. It flags gaps where provenance chains break or correlation identity is lost.

Can audit history be used as current state in queries?▼

No. The Skill enforces that current state is read from its owning tables and resolvers, never reconstructed opportunistically from activity_events. History explains how state was reached but must not substitute for current-state reads unless the domain is explicitly event-sourced.

What happens when a required audit write fails during a mutation?▼

If the audit write is transactionally required, state and history must commit atomically or the mutation must fail and roll back. Durable asynchronous delivery must remain observable, retryable, correlated, and idempotent; best-effort failures must surface honestly.

When should I not use this audit reviewer?▼

Do not use it for current truth and findings logic, which belongs to the truth-engine reviewer, or for workflow execution state, which belongs to the execution reviewer. Runtime RLS safety and migration rollout are also owned by sibling reviewers.