compliance-auditability

Design audit logs, traceability links, and verifiable evidence for compliance-sensitive systems.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill compliance-auditability-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compliance-auditability
Source: https://github.com/pnewsam/skills/tree/main/archive/platform-compliance-evicted/compliance-auditability
Command: npx skills add https://github.com/pnewsam/skills --skill compliance-auditability-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams in regulated environments struggle to prove what changed, who approved it, and how a risk was resolved. This Skill provides engineering guidance for building machine-verifiable audit trails, change records, and remediation evidence directly into the development workflow. ## Core Features & Use Cases - Audit Log Design: Enforces a schema where every audit event carries actor, resource, action, timestamp, result, and context, validated by automated tests. - Traceability & Evidence Linking: Connects PRs to alerts, tickets, decisions, and deployments with stable links that survive retention policies. - Risk Acceptance Governance: Requires owner, rationale, expiry, and compensating controls before any risk acceptance is recorded. - Use Case: When closing a vulnerability remediation, use this Skill to ensure the PR links the advisory ID, affected and fixed versions, scanner results, and regression tests so an auditor can reconstruct the full chain. ## Quick Start Ask the agent to review your change workflow and design audit evidence for a sensitive action, including the log schema, traceability links, and risk-acceptance fields.

Frequently Asked Questions about compliance-auditability

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

FAQPage Schema
How do I design an audit log for compliance requirements?▼

Design each audit event to carry actor, resource, action, timestamp, result, and context, then enforce that schema with an automated test. Keep logs structured and queryable so they can answer who did what, when, and with what result.

What evidence is needed for vulnerability remediation?▼

Vulnerability remediation evidence includes the advisory ID, affected and fixed versions, a clean scanner result, and regression tests. Link all of these from the PR so the remediation chain is reconstructible later.

How should risk acceptance be documented?▼

Risk acceptance requires a named owner, rationale, expiry date, and compensating controls before it is recorded. Time-box exceptions and create a follow-up issue rather than accepting permanent risk without review.

Can audit logs contain sensitive data like PII or secrets?▼

No, audit logs should never contain secrets, PII, or ePHI to prove access occurred. Redact sensitive payloads while still recording actor, action, resource, timestamp, and result.

When should compliance evidence decisions be escalated?▼

Records retention scope, audit scope, and regulatory evidence requirements stay with the designated audit owner. This guidance covers engineering evidence practices, not legal advice.