Claude-skill-registry audit_logging
Ensure every critical action is logged (vital for UAG/Trust Room).
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/audit-logging-cityfish91159-maihouses" ~/.claude/skills/majiayu000-claude-skill-registry-audit-logging && rm -rf "$T"
manifest:
skills/data/audit-logging-cityfish91159-maihouses/SKILL.mdsource content
Audit Logging Protocol
1. Principles
- No Invisible Actions: Every state-changing API call (POST, PUT, DELETE) must produce a log entry.
- Traceability: Logs must include
,userId
,action
, andresourceId
.metadata
2. Implementation Standards
- Backend (API):
- Use the project's standard Logger service (e.g.,
or similar).src/services/logger.ts - Example:
await Logger.info({ event: 'POST_CREATED', userId: user.id, metadata: { postId: newPost.id }, });
- Use the project's standard Logger service (e.g.,
- Database (Supabase):
- Ensure tables have
,created_at
, andupdated_at
columns.created_by - Check if specific Audit Table inserts are required (e.g.
table).audit_logs
- Ensure tables have
3. Verification Checklist
- Does the new API endpoint call
?Logger - Are logs visible in Supabase/Dashboards?
- Is the log level appropriate (Info vs Error)?
- Does the log contain enough context to debug issues later?