/review-evidence
Review and validate evidence artifacts against control requirements
$ npx -y skills add GRCEngClub/claude-grc-engineering --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/review-evidence
Context preview
What this command does when you run it.
Review and validate evidence artifacts against control requirements
Command definition
review-evidence.mddescription: Review and validate evidence artifacts against control requirements
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
- Gaps identified
- Recommendations
Examples
# 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
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Repo: GRCEngClub/claude-grc-engineering
Other commands on trust-center.
- /research
Start or resume an academic research project โ idea through literature, methodology, writing, feedback, and publishing
Open command - /collect
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
Open command - /setup
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
Open command - /status
Check the deployment status of the trust center.
Open command - /scan
Run testssl.sh against one or more HTTPS endpoints and emit v1 Findings mapped to SOC 2, NIST 800-53, PCI DSS 4.0.1, ISO 27001, and SCF controls.
Open command - /compliance-posture
Serve a localhost compliance posture dashboard from monitor-continuous JSON
Open command

