audit

Review audit logs, decision traces, and PDCA session history from local JSONL files.

2|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/solitasroh/mcukit --skill audit-solitasroh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/solitasroh/mcukit/tree/main/skills/audit
Command: npx skills add https://github.com/solitasroh/mcukit --skill audit-solitasroh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a unified view of audit logs, decision traces, and PDCA session history to improve transparency and accountability.

Core Features & Use Cases

  • View recent audit log entries
  • Show decision traces for a feature
  • Show daily/weekly summaries
  • Search logs by action, feature, or date
  • Review session history for governance and debugging

Quick Start

Open Claude Code and run /audit to see the latest entries

Frequently Asked Questions about audit

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

FAQPage Schema
How do I view audit logs and decision traces for debugging?

Search audit logs by action, feature, or date using the search functionality defined in the Skill's frontmatter, which scans local JSONL log files and decision records to retrieve matching entries for governance review.

Can I generate daily or weekly summaries from PDCA session history?

Yes, you can generate daily and weekly summaries from PDCA session history by applying the summary action, which consolidates decision traces and audit log entries into readable reports for accountability tracking.

Does the audit Skill work with MCU, MPU, and WPF workflows?

The audit Skill applies across MCU, MPU, and WPF workflows, offering read-only access to review recent activity, trace decisions, and generate summaries for transparency and debugging within those environments.

What format do audit logs need to be in for trace and summary actions?

Audit logs must be stored as local JSONL files, alongside decision files, so the Skill can perform read-only access to execute log, trace, summary, and search actions for governance and debugging purposes.

Why use a read-only audit trail tool instead of editing logs directly?

A read-only audit trail tool ensures transparency and accountability by preserving the integrity of JSONL logs and decision histories, preventing accidental modification while allowing users to review session history and trace decisions safely.