Stats
Actions
Tags
From grc-auditor
Review and validate evidence artifacts against control requirements
How this command is triggered — by the user, by Claude, or both
Slash command
/grc-auditor:review-evidenceThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Review Evidence Reviews evidence artifacts to validate they satisfy control requirements. ## Arguments - `$1` - Evidence file or directory path (required) - `$2` - Control ID or framework (optional) ## Instructions 1. Analyze the provided evidence artifacts for: - Completeness (does it cover the control requirement?) - Timeliness (is the evidence current?) - Relevance (does it actually demonstrate the control?) - Authenticity (are there signs of tampering or inconsistency?) 2. Generate an evidence review report including: - Evidence summary - Control mapping - G...
Reviews evidence artifacts to validate they satisfy control requirements.
$1 - Evidence file or directory path (required)$2 - Control ID or framework (optional)Analyze the provided evidence artifacts for:
Generate an evidence review report including:
# Review SOC 2 evidence
/grc-auditor:review-evidence ./evidence/access-reviews.pdf CC6.1
# Review PCI-DSS evidence
/grc-auditor:review-evidence ./evidence/mfa-logs.pdf 8.4.2
# Review ISO 27001 evidence
/grc-auditor:review-evidence ./evidence/backup-policy.pdf A.12.3.1
npx claudepluginhub vantainc/claude-grc-engineering --plugin grc-auditor7plugins reuse this command
First indexed Apr 26, 2026
Showing the 6 earliest of 7 plugins
/review-evidenceReviews evidence artifacts like files or directories against control requirements or frameworks, generating a report on completeness, gaps, and recommendations.