sauron-watch

Automates R017 verification across manager agents, registries, and documentation before committing code.

34|5|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/baekenough/oh-my-customcode --skill sauron-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sauron-watch
Source: https://github.com/baekenough/oh-my-customcode/tree/main/templates/.claude/skills/sauron-watch
Command: npx skills add https://github.com/baekenough/oh-my-customcode --skill sauron-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronizes and verifies all agents, commands, and documentation before committing changes, preventing misconfigurations and drift.

Core Features & Use Cases

  • Phase-driven verification (5 rounds for manager agents) plus deep reviews (3 rounds) to ensure alignment.
  • Checks cover agent dependencies, registry synchronization, updated docs, and orchestrator manage sections.
  • Provides a ready-to-commit readiness assessment and actionable fixes when issues are found.

Quick Start

Initialize the sauron-watch workflow to perform full R017 verification before committing.

Frequently Asked Questions about sauron-watch

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

FAQPage Schema
How do I enforce multi-round verification before committing code in an orchestrator-driven workflow?

You can automate full verification across manager agents, registries, and documentation before committing code. This process applies phase-structured checks with 5 rounds for manager agents and 3 deep review rounds to catch inconsistencies and ensure readiness.

What is R017 verification and when do I need it for agent management?

R017 verification is a phase-structured validation process that synchronizes and verifies all agents, commands, and documentation. You need it before committing changes in orchestrator-driven workflows to prevent misconfigurations and drift across agent dependencies and registries.

How do I check agent dependencies and registry synchronization before a commit?

You can check agent dependencies and registry synchronization by initializing a verification workflow that scans orchestrator manage sections, validates registry alignment, and confirms updated documentation. It provides a ready-to-commit readiness assessment with actionable fixes for any issues found.

Does commit validation work with orchestrator-driven workflows that use multiple manager agents?

Commit validation works with orchestrator-driven workflows by applying multi-round verification specifically designed for manager agents. It runs 5 verification rounds for manager agents plus 3 deep review rounds to ensure alignment and enforce commit readiness guardrails.

What's the best way to prevent documentation drift and misconfigurations before committing changes?

The best way to prevent drift and misconfigurations is to automate full verification that checks agent dependencies, registry synchronization, updated docs, and orchestrator manage sections. This provides a readiness assessment and actionable fixes before code is committed.

Why does my code commit fail readiness checks in an agent management workflow?

Commit readiness checks fail when verification detects inconsistencies across agents, commands, or documentation. Running phase-structured checks with deep reviews identifies specific misconfigurations, registry sync issues, or outdated docs, and provides actionable fixes to resolve them.