audit-log
Skill4 starsChanged 4 months agoISCView 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.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- berriosb/data-analytics-agentstheir own version, first seen Oct 20, 2026
- EmeaAppGbb/spec2cloudword for word, first seen Oct 9, 2026
- BuilderIO/agent-nativetheir own version, first seen Oct 8, 2026
- Pradnyeshp/Claude-Skillstheir own version, first seen Jul 6, 2026
- thebharathkumar/agent-flight-recordertheir own version, first seen Jul 5, 2026
- SAQLAINAP/GitClaw-Agenttheir own version, first seen Apr 5, 2026
Other versions7 projects use a version of this.
Word for word · 1
- EmeaAppGbb/spec2cloud★ 100100% same
Edited · 0
None found.
Wrote their own version · 6
- BuilderIO/agent-native★ 7.6ksame name
- Pradnyeshp/Claude-Skills★ 2same name
- SAQLAINAP/GitClaw-Agent★ 1same name
- berriosb/data-analytics-agents★ 0same name
- PalmCoast/clawlock-plugin★ 0same name
- thebharathkumar/agent-flight-recorder★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- adrSkill
- api-extractorSkill
- architecture-mapperSkill
- aspireSkill
- azure-app-registrationSkill
- azure-deploymentSkill
- bug-fixSkill
- build-checkSkill
- cloud-native-assessmentSkill
- cloud-native-plannerSkill
- codebase-scannerSkill
- commit-protocolSkill
- contract-generationSkill
- data-model-extractorSkill
- ddd-modelingSkill
- dependency-inventorySkill
- deploy-diagnosticsSkill
- dev-implementerSkill
- e2e-generationSkill
- error-handlingSkill
- extension-plannerSkill
- find-skillsSkill
- frd-generatorSkill
- gherkin-generationSkill
- human-gateSkill
- implementationSkill
- modernization-assessmentSkill
- modernization-plannerSkill
- performance-assessmentSkill
- playwright-cliSkill
- pm-issue-authorSkill
- prd-generatorSkill
- release-managerSkill
- research-best-practicesSkill
- resumeSkill
- rewrite-assessmentSkill
- rewrite-plannerSkill
- security-assessmentSkill
- security-plannerSkill
- skill-creatorSkill
- skill-discoverySkill
- spec-refinementSkill
- spec-validatorSkill
- state-managementSkill
- tech-stack-resolutionSkill
- test-discoverySkill
- test-generationSkill
- test-runnerSkill
- ui-ux-designSkill
The file
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
- Distinctive: line 45
Every audit log entry MUST contain ALL of the following fields:
“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.
Files
Audit Log Protocol
Append every significant action to .spec2cloud/audit.log. Never overwrite — always append.
Format
[ISO-timestamp] phase=PHASE action=ACTION result=RESULTWhat 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-2failEvery increment transition
[2026-02-09T14:30:00Z] increment=walking-skeleton action=increment-delivered result=transition-to-resource-crudEvery 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=orincrement=(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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

