keystone:review

Automate semantic code review of diffs with functional, security, risk, and deployment checks.

42|3|Updated May 31, 2026
One-click install
npx skills add https://github.com/tacoda/keystone --skill keystone-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keystone:review
Source: https://github.com/tacoda/keystone/tree/main/internal/framework/scaffold/templates/charter/skills/keystone-review
Command: npx skills add https://github.com/tacoda/keystone --skill keystone-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the code review process for diffs, providing comprehensive checks for functionality, security, risk, and deployment.

Core Features & Use Cases

  • Functional Review: Ensures changes adhere to specifications.
  • Security Review: Checks for authentication, input validation, secrets, and injection.
  • Risk Review: Evaluates blast radius, data integrity, and observability.
  • Deployment Review: Inspects migrations, rollback, configuration, and infrastructure dependencies.
  • Use Case: After running a successful verification with /keystone:verify, use this Skill to conduct a semantic review before opening a Pull Request.

Quick Start

Run the keystone:review skill to initiate a semantic review of the current diff.

Frequently Asked Questions about keystone:review

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

FAQPage Schema
How do I automate semantic code review for diffs before opening a pull request?

Automated diff review evaluates functional adherence, security vulnerabilities, risk blast radius, and deployment configurations using inferential sensors. This semantic analysis replaces manual checks by inspecting migrations, rollback plans, authentication, and input validation directly in the diff.

What does automated security review check for in a code diff?

Automated security review checks diffs for authentication issues, input validation flaws, exposed secrets, and injection vulnerabilities. These inferential sensors trigger during the semantic review stage to identify potential security threats before code deployment.

Can I run semantic risk review on my repository diffs without a verification step?

Semantic risk review requires a clean verification step beforehand. You must run a successful verification using the appropriate workflow command before initiating the review sensors to evaluate blast radius, data integrity, and observability metrics.

How does automated deployment review inspect infrastructure dependencies in diffs?

Automated deployment review inspects diffs for database migrations, rollback configurations, infrastructure dependencies, and deployment settings. It triggers inferential sensors during the semantic review stage to ensure repository changes are safely deployable.

When do I need automated functional review for my development workflow?

You need automated functional review during the code review stage of your development workflow, after running a successful verification. It ensures your diff changes adhere to specifications before you open a Pull Request for broader team evaluation.