review-evidence

Name: review-evidence
Availability: InStock
Author: graysurf

Consolidate review findings, validations, artifacts, and verification status into a JSON record.

Updated Aug 23, 2026

Search Tags:#verification #audit #evidence #review #artifact-management #nils-cli

Ready to run

npx skills add https://github.com/graysurf/agent-runtime-kit --skill review-evidence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-evidence
Source: https://github.com/graysurf/agent-runtime-kit/tree/main/tests/golden/claude/plugins/evidence/skills/review-evidence/expected
Command: npx skills add https://github.com/graysurf/agent-runtime-kit --skill review-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persisting and organizing review findings, validation commands, artifacts, and verification status across PR workflows.

Core Features & Use Cases

Initialize and allocate a per-review record directory
Record findings with severity, paths, optional line, and summary
Attach validations and artifacts and generate a verifiable JSON record
Verify and export a structured review_evidence.json for downstream tooling

Quick Start

Initialize a new review, record a finding, attach validations, and generate the JSON evidence record.

Frequently Asked Questions about review-evidence

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

FAQPage Schema

How do I persist and organize code review findings for audit workflows?▼

To persist and organize code review findings for audit workflows, initialize a per-review record directory, record findings with severity and paths, and generate a verifiable JSON evidence record.

What's the best way to attach validation commands and artifacts to a pull request review?▼

Attaching validation commands and artifacts to a pull request review involves recording validations alongside findings in a dedicated review directory, then exporting a structured review_evidence.json record for downstream tooling.

How does the nils-cli review-evidence command structure verification status?▼

The nils-cli review-evidence command structures verification status by allocating a per-review record directory, initializing the review, recording findings and validations, and producing a verifiable JSON record.

Can I export a structured JSON record of code review findings for downstream tooling?▼

Yes, you can export a structured JSON record of code review findings for downstream tooling by verifying and exporting the review_evidence.json file, which consolidates findings, validations, and artifact attachments.

Do I need to allocate a specific directory to archive pull-request validation evidence?▼

Allocating a per-review record directory is required to archive pull-request validation evidence, ensuring that findings, validation commands, and artifacts are persisted and traceable across workflows.

What limitations exist when recording audit evidence for code reviews?▼

When recording audit evidence for code reviews, limitations include dependencies on the nils-cli command structure and the requirement to initialize a per-review directory before attaching artifacts or generating the JSON record.