agentleFS
Sign inStart free
EmeaAppGbbEmeaAppGbb/spec2cloud/.github/skills/audit-log/SKILL.md

audit-log

Skill100 starsChanged 7 months agoMITView on GitHub

Append structured entries to .spec2cloud/audit.log for every significant action. Never overwrite, always append. Use when logging task execution, increment transitions, human gate events, or errors.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every audit log entry MUST contain ALL of the following fields:

    line 45

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit Log Protocol

Append every significant action to .spec2cloud/audit.log. Never overwrite — always append.

Format

[ISO-timestamp] phase=PHASE action=ACTION result=RESULT

What to Log

Every task execution

[2026-02-09T14:15:00Z] increment=resource-crud step=implementation slice=api iteration=1 action=write-code result=tests-3pass-2fail

Every increment transition

[2026-02-09T14:30:00Z] increment=walking-skeleton action=increment-delivered result=transition-to-resource-crud

Every human gate event

[2026-02-09T14:35:00Z] increment=resource-crud step=tests action=human-gate result=gherkin-approved
[2026-02-09T14:35:00Z] phase=discovery step=specs action=human-gate result=rejected feedback="missing error states for auth"

Every error

[2026-02-09T14:40:00Z] phase=deployment action=azd-provision result=error message="quota exceeded in eastus"

Mandatory Completion Checklist

Every audit log entry MUST contain ALL of the following fields:

  • ISO-8601 timestamp (e.g., 2026-02-09T14:40:00Z)
  • Context identifier: phase= or increment= (what work is being done)
  • action= field (what specific action was taken)
  • result= field (outcome: done, error, approved, rejected, etc.)
  • message= field for errors and rejections (human-readable detail)

BLOCKING: An audit entry missing any required field makes the audit trail incomplete. The orchestrator must ensure every append follows this schema.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free