azoth-review-insights

Automate cursor-oriented blindspot reviews and write D32 insights to .azoth/inbox/.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill azoth-review-insights
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azoth-review-insights
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-review-insights
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-review-insights

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates a cursor-oriented blindspot review and surfaces structured insights to accelerate quality checks during Codex-driven workflows.

Core Features & Use Cases

  • Automates cursor-oriented blindspot reviews across code editors and prompts.
  • Writes D32 insights to the .azoth/inbox/ for downstream processing.
  • Use Case: During code reviews or prompt tuning, run this skill to reveal hidden issues and capture actionable insights.

Quick Start

Prompt the system to perform a cursor-oriented blindspot review and write D32 insights to .azoth/inbox/.

Frequently Asked Questions about azoth-review-insights

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

FAQPage Schema
What is a cursor-oriented blindspot review and when do I need it?

A cursor-oriented blindspot review is an automated process that surfaces hidden issues during code reviews or prompt tuning. You need it during Codex-driven workflows to reveal real-world problems and capture actionable insights for quality checks.

How do I run a blindspot review and write insights to my inbox?

To run a blindspot review and write insights to your inbox, prompt the system to perform a cursor-oriented review. The skill reads guidance from review-insights.md, preserves stage structure, and outputs D32 insights to the .azoth/inbox/ directory.

Does the blindspot review skill work across different code editors and prompts?

Yes, the blindspot review skill works across code editors and prompts. It applies during Codex-driven review or debugging sessions, reading guidance from .claude/commands/review-insights.md and writing structured D32 insights to the .azoth/inbox/.

What is the best way to surface hidden issues during Codex-driven debugging sessions?

The best way to surface hidden issues during Codex-driven debugging is to run an automated cursor-oriented blindspot review. This captures actionable D32 insights and writes them directly to the .azoth/inbox/ for downstream processing.

Are there prerequisites for writing D32 insights to the .azoth inbox?

Yes, writing D32 insights to the .azoth inbox requires the .claude/commands/review-insights.md guidance file to exist. The skill reads this file to preserve the command's stage structure and agent binding before outputting results with azoth_effect: write.