Claude Skills · Code Review & Testing
Hyper Docs Loop
zeikar/hyperclaudeUse when documentation should be brought into accuracy with the code in one gesture — Codex docs-review → fix → re-review, repeated until no blocking findings remain. Also when the user invokes /hyperclaude:hyper-docs-loop. For manual round-by-round control use /hyperclaude:hyper-docs-review + manual edits instead. Requires the experimental agent-teams feature.
At a glance
This skill is for Code Review & Testing and helps you synchronize documentation with code, review documentation for accuracy, and iteratively fix documentation gaps.
/plugin marketplace add zeikar/hyperclaude
/plugin install hyper-docs-loop
Setup, runtime and requirements describe zeikar/hyperclaude, the repo this skill ships in.
documentationcode-reviewAutomated FixesIterationSynchronizationagent-teams
Also in zeikar/hyperclaude
View the repoUse when plan-harden → implement-harden should chain in one gesture — hyper-plan-loop produces a clean plan, then hyper-implement-loop execu...
Use after producing code changes that should be critiqued — before commit or merge. The default for a natural-language code review of the us...
Use when encountering a test failure, exception, regression, or unexpected behavior — before proposing fixes. Also when the user invokes /hy...
Use after documentation edits — typically after the documenter agent runs, or when the user invokes /hyperclaude:hyper-docs-review. Runs Cod...
Use after implementation changes documented API, schemas, CLI flags, or architecture — before docs go stale. Also when the user invokes /hyp...
Use when about to execute a multi-task plan from .hyperclaude/plans/. Also when the user invokes /hyperclaude:hyper-implement. Runs each tas...
Use when a plan should be executed end-to-end and critic-hardened in one gesture — implement → Codex code-review → fix, repeated until clean...
Use when starting from a vague or under-specified idea and want requirements clarified before planning — "interview me", "ask me what you ne...
Use on-demand to extract evidence-anchored repo-local knowledge candidates from accumulated .hyperclaude/ artifacts (plans/done, plan-review...
Use when about to start a non-trivial implementation that needs decomposition before coding. Also when the user invokes /hyperclaude:hyper-p...
Use when a plan should be produced and critic-hardened in one gesture — plan → Codex review → revise, repeated until clean. Also when the us...
Use after a plan exists in .hyperclaude/plans/ and should be sanity-checked before execution. Also when the user invokes /hyperclaude:hyper-...
Other Code Review & Testing skills
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests,...
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold e...
Use when you need to resolve an in-progress git merge/rebase conflict.
A relentless interview that asks every frontier question at once, round by round.