audit_logging

Audit Logging Protocol

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "audit_logging" with this command: npx skills add cityfish91159/maihouses/cityfish91159-maihouses-audit-logging

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 , resourceId , and metadata .

  1. Implementation Standards
  • Backend (API):

  • Use the project's standard Logger service (e.g., src/services/logger.ts or similar).

  • Example: await Logger.info({ event: 'POST_CREATED', userId: user.id, metadata: { postId: newPost.id }, });

  • Database (Supabase):

  • Ensure tables have created_at , updated_at , and created_by columns.

  • Check if specific Audit Table inserts are required (e.g. audit_logs table).

  1. 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?

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

draconian_rls_audit

No summary provided by upstream source.

Repository SourceNeeds Review
Security

security_audit

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

agentic_architecture

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

code-review-excellence

No summary provided by upstream source.

Repository SourceNeeds Review