kasmos-reviewer

Automate code review against predefined criteria for correctness and spec compliance.

5|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/kastheco/kasmos --skill kasmos-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kasmos-reviewer
Source: https://github.com/kastheco/kasmos/tree/main/.agents/skills/kasmos-reviewer
Command: npx skills add https://github.com/kastheco/kasmos --skill kasmos-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, mcp__kasmos__docs_search, mcp__kasmos__docs_read, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring that changes are correct and compliant with specifications, saving time and reducing errors.

Core Features & Use Cases

  • Structured Review: Provides a structured review process with a checklist for correctness, spec compliance, and code quality.
  • Worktree Awareness: Ensures that reviews are worktree-aware, focusing on changes since the task branch diverged.
  • Integration Hazards: Checks for signal consistency, config keys, FSM transitions, and operator labels across the codebase.
  • Self-Fix Protocol: Offers guidance on self-fixing minor issues or escalating to the coder for more complex ones.
  • Verification Before Approval: Ensures that all checks pass before approving changes, including formatting, static analysis, and spelling checks.

Quick Start

Run the kasmos-reviewer skill to review the code changes in the current branch.

Frequently Asked Questions about kasmos-reviewer

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

FAQPage Schema
How do I automate code review for spec compliance in git?

Automating code review for spec compliance involves comparing branch changes against predefined criteria. This process uses git and MCP tools to check correctness, signal consistency, and configuration keys before approving modifications.

What is the best way to ensure code changes pass formatting and static analysis checks?

Ensuring code changes pass formatting and static analysis requires a verification protocol before approval. Reviews apply structured checklists to validate spelling, formatting, and static analysis, escalating complex failures to the coder.

Does this code review process work with existing MCP tools?

Yes, the code review process integrates directly with MCP tools. It uses docs_search and docs_read dependencies to compare changes against specifications, ensuring modifications maintain signal consistency and FSM transitions across the worktree.

How do I review only the code changes in my current git worktree branch?

Reviewing code changes in a git worktree requires worktree-aware checks that focus on modifications since the task branch diverged. The process isolates branch-specific updates to verify correctness and spec compliance without reviewing unrelated code.

What should I do when a code review identifies integration hazards like inconsistent operator labels?

When code review identifies integration hazards like inconsistent operator labels, apply the self-fix protocol to resolve minor issues. For complex hazards affecting FSM transitions or signal consistency, escalate the changes to the coder.