Category

Docs AI Agent Loops

Documentation sync, README, AGENTS.md, and project context loops. Every page is server-rendered, source-aware, and includes a copy-ready Markdown protocol.

All categories · 3 loops

All Docs loops

Docsmanual trigger Hardened

AGENTS.md Improvement Loop

Audit and improve repository agent instructions so future AI sessions follow project conventions and verification rules.

Claude CodeCodexCursor

agents-mdproject-contextinstructions

Kickoff preview

Audit repository agent instructions against actual project files, then improve them with accurate commands, architecture rules, and verification expectations.
Goal: Make repository instructions accurate, actionable, and verification-oriented.
Check command: ls -la && rg -n "build|test|lint|deploy" README.md package.json AGENTS.md CLAUDE.md
Exit condition: Agent instructions state stack, commands, architecture rules, and verification expectations accurately.
Max iterations: 3
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not invent commands, tools, or architecture claims that are not present in the repository.

Docsevent trigger Hardened

Docs Sync After Edits

After behavior or API changes, update README, docs, examples, and project instructions to match the code.

CursorClaude CodeCodex

docsreadmechangelog

Kickoff preview

Review code changes for documentation impact, update relevant docs/examples/instructions, and report evidence or why no docs update is needed.
Goal: Keep documentation aligned with code changes.
Check command: git diff --name-only HEAD
Exit condition: Docs are updated for relevant changes or the no-docs-needed decision is justified.
Max iterations: 3
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not update docs with behavior that the code does not actually implement.

Docsmanual trigger Hardened

Claude Code Hooks Setup

Plan and validate Claude Code hook rules for post-edit verification, pre-commit scanning, and safe stop behavior.

Claude Code

claude-codehooksautomation

Kickoff preview

Design Claude Code hooks for this repository. Define hook goals, allowed commands, risks, and manual verification before enabling them.
Goal: Design Claude Code hooks that improve safety without blocking legitimate work.
Check command: rg -n "hooks|PostToolUse|PreToolUse|Stop" .claude AGENTS.md CLAUDE.md
Exit condition: Hook behavior is documented, scoped, safe, and testable.
Max iterations: 3
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not enable hooks that run destructive commands without explicit human approval.

Why this category matters

Docs loops are useful because AI agents need explicit feedback gates and exit criteria. A plain prompt may produce a first draft; a loop tells the agent how to verify progress, handle failures, and stop with evidence.