Review Change
Review a completed change against its authorizing spec in fresh context — evidence-based checks, severity-ranked findings, and a written verdict for the human's merge decision. Use when a diff needs reviewing before merge, or when add-feature / fix-bug / implement-spec reaches its review gate.
Install
$ agentstack add skill-kunalsuri-ai-fication-kit-review-change ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-kunalsuri-ai-fication-kit-review-change) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Review a change
The contract: review in a session that did NOT write the change; check with evidence, not assertions; re-run the suites yourself; the written verdict is the deliverable — the human merges, not you.
1. Fresh-context gate
A reviewer sharing the implementer's context inherits the implementer's blind spots. If this session wrote the change, stop and hand the review to a fresh session that did not implement it.
2. Pin the scope
Identify the exact diff (commits / branch / files) and the spec or bugfix doc in ai/lab/specs/ that authorized it. No spec ⇒ that is finding #1, severity blocker: unspecced work.
3. Open the review
Copy ai/lab/reviews/REVIEW_TEMPLATE.md → ai/lab/reviews/REVIEW_.md.
4. Check with evidence
For each check in the template — spec conformance, surgical diff, Stability respected, tests, conventions, knowledge updated, provenance clean — record where you looked and what you saw. Delegate the suite re-run to test-runner: run the suites the spec names yourself; do not trust the implementer's report.
5. File findings by severity
Any blocker or major ⇒ verdict request-changes; hand the list back to the implementer. Minor / nit findings can ship with notes.
6. Verdict and hand-off
Fill "what the human should double-check" — the judgement calls a mechanical check cannot make. The review itself is [inferred]; the human's merge decision is the real approval, and this document is its evidence.
7. Record
Link the review from the work's row in ai/lab/WORKLOG.md (Review column) and set that row's Status to in-review.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kunalsuri
- Source: kunalsuri/ai-fication-kit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.