audit-log

Append structured audit log entries to .spec2cloud/audit.log.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill audit-log-emeaappgbb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-log
Source: https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield/tree/main/.github/skills/audit-log
Command: npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill audit-log-emeaappgbb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The audit-log Skill solves the problem of tracking and auditing every significant action within a development workflow, ensuring traceability and maintaining an immutable log of all events.

Core Features & Use Cases

  • Immutable Audit Logging: Append structured log entries to .spec2cloud/audit.log without overwriting existing data.
  • Task Execution Tracking: Log the execution of every task, including success or failure outcomes.
  • HumanGate Events: Record every human interaction and approval within the development workflow.
  • Error Tracking: Capture and log errors with detailed messages for debugging and troubleshooting.
  • Use Case: Imagine you need to audit the changes and transitions in a development phase. This Skill ensures that every action, approval, and error is documented, allowing you to review the development history at any time.

Quick Start

Enable the audit-log skill within your project to automatically track and append audit entries for all significant actions.

Frequently Asked Questions about audit-log

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

FAQPage Schema
How do I ensure traceability and audit every significant action in a development workflow?

To ensure traceability, you append structured log entries to an audit log without overwriting existing data. This records task executions, HumanGate approvals, and errors for compliance and post-mortem analysis.

What is the required format for structured audit logging in a software development environment?

The required format for structured audit logging is `[ISO-timestamp] phase=PHASE action=ACTION result=RESULT`. This ensures consistent traceability and non-destructive auditing of all development activities.

Can I use audit logging to track human approval events and errors for post-mortem analysis?

Yes, audit logging captures HumanGate events to record human interactions and approvals, alongside detailed error tracking. This provides critical action history for debugging and post-mortem analysis.

Does audit logging overwrite existing data when tracking development process actions?

No, audit logging appends structured entries to `.spec2cloud/audit.log` without overwriting existing data. This maintains an immutable log of all events, ensuring non-destructive auditing and accuracy.

Do I need to manually verify audit log entries for accuracy in a DevOps pipeline?

Yes, the audit logging process requires manual verification of all entries for accuracy. This ensures the immutable log reliably supports compliance, traceability, and post-mortem analysis.