doc-review

스타11

포크2

업데이트2026년 5월 12일 18:29

Open a plan, research, or design doc in Plannotator's browser UI for human review and act on the returned annotations. Use when the user says "review the plan", "open the doc in plannotator", "let me annotate the research", "review the latest doc", or returns to a session to gate work the agent produced.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

hay-kot

hay-kot/dotfiles

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Doc Review

Open a markdown document in Plannotator with --gate, then act on the user's annotations in the same conversation. The --gate flag blocks until the user approves or denies, and returns their feedback as command output.

Argument handling

$ARGUMENTS controls which doc opens:

Argument	Behavior
empty	Newest `.md` across `.hive/plans/`, `.hive/research/`, `.hive/design-docs/`
`plans`	Newest `.md` in `.hive/plans/`
`research`	Newest `.md` in `.hive/research/`
`design-docs`	Newest `.md` in `.hive/design-docs/`
any path	That file directly (relative to cwd or absolute)
any URL	That URL (Plannotator handles `https://` natively)

To find the newest file, use find with -printf (or stat on macOS) and pick the highest mtime. Resolve .hive/ via the symlink — do NOT use Glob, it won't follow it. If the symlink doesn't exist, run hive ctx init first.

If no candidate file is found, tell the user which directory was empty and stop. Don't guess a path.

Run

plannotator annotate <resolved-path-or-url> --gate

Don't ask the user to copy the command into a terminal — run it yourself.

After plannotator returns

Annotations returned — address each one in the same conversation. If the document needs edits, edit the file, summarize what changed, and offer to re-gate.
Approval / LGTM — acknowledge briefly and continue with whatever the doc was setting up (implementation, next research question, etc.).
Denied with no actionable feedback — ask the user what they'd like changed before re-gating.
Session closed without feedback — say so in one sentence and continue.

Notes

--gate is the right mode for this skill; it's the synchronous review primitive.
Plannotator returns its result on the same CLI invocation, so the agent sees the annotations in the next tool turn — no polling, no separate hook.
If the user wants async review (close the session, come back later), they should use hive todo add --uri "review://<path>" instead — that's a different workflow and not what this skill is for.

이 저장소의 다른 Skills

같은 저장소

hay-kot/dotfiles

Best practices for working with Go codebases. Use when writing, debugging, or exploring Go code, including reading dependency sources and documentation.

2026-07-1611

hc-loop

hay-kot/dotfiles

Autonomous orchestration loop for hive hc tasks. The high-capability manager model reads pending tasks, delegates implementation to cheaper worker sub-agents, critically reviews their output, and commits only code that passes quality checks. Runs to completion without stopping to ask questions.

2026-07-1311

rethink

hay-kot/dotfiles

Post-implementation design re-evaluation. After a feature reaches a working state through iteration, step back and re-examine what actually got built: are the data structures and algorithms the right fit for the access patterns that emerged, can code paths that grew through iteration be consolidated, and what iteration residue (tests for abandoned designs, dead flags/scaffolding, debug logging) should be deleted. Produces a tiered proposal report and applies only approved changes. Use when the user says "rethink this", "step back and re-evaluate", "is this the right design/data structure", "apply CS fundamentals", or wants a design pass on a working feature branch before PR. Not for bug-hunting (/review) or expression-level polish (/simplify) — this questions the design those skills preserve.

2026-07-0411

agent-orchestrator

hay-kot/dotfiles

Orchestrate parallel claude and codex CLI agents through tmux to deliver a feature end-to-end. The orchestrator delegates planning, work, and review to spawned agents in tmux windows; it does NOT write or edit code itself. User-invoked only.

2026-07-0111

diff-review

hay-kot/dotfiles

Open the current branch's diff (or a specific PR) in Plannotator's browser-based code review UI and act on the returned feedback. Use when the user says "review my changes in plannotator", "open the diff for review", "review this PR in plannotator", "let me annotate the diff", or returns to a session to gate code the agent produced.

2026-07-0111

review

hay-kot/dotfiles

Single-pass code review of the current branch (or a diff) that routes the changes to relevant concerns, dispatches fresh-context reviewer sub-agents, verifies findings to strip false positives, and reports a ranked, evidence-backed review. Use when the user asks to review local changes, a branch, or a PR before it goes to humans.

2026-07-0111

name	doc-review
description	Open a plan, research, or design doc in Plannotator's browser UI for human review and act on the returned annotations. Use when the user says "review the plan", "open the doc in plannotator", "let me annotate the research", "review the latest doc", or returns to a session to gate work the agent produced.
allowed-tools	Bash(plannotator:),Bash(hive ctx ls),Bash(ls:),Bash(find:),Bash(stat:),Read
disable-model-invocation	true

Doc Review

Argument handling

$ARGUMENTS controls which doc opens:

Argument	Behavior
empty	Newest `.md` across `.hive/plans/`, `.hive/research/`, `.hive/design-docs/`
`plans`	Newest `.md` in `.hive/plans/`
`research`	Newest `.md` in `.hive/research/`
`design-docs`	Newest `.md` in `.hive/design-docs/`
any path	That file directly (relative to cwd or absolute)
any URL	That URL (Plannotator handles `https://` natively)

If no candidate file is found, tell the user which directory was empty and stop. Don't guess a path.

Run

plannotator annotate <resolved-path-or-url> --gate

Don't ask the user to copy the command into a terminal — run it yourself.

After plannotator returns

Annotations returned — address each one in the same conversation. If the document needs edits, edit the file, summarize what changed, and offer to re-gate.
Approval / LGTM — acknowledge briefly and continue with whatever the doc was setting up (implementation, next research question, etc.).
Denied with no actionable feedback — ask the user what they'd like changed before re-gating.
Session closed without feedback — say so in one sentence and continue.

Notes

--gate is the right mode for this skill; it's the synchronous review primitive.
Plannotator returns its result on the same CLI invocation, so the agent sees the annotations in the next tool turn — no polling, no separate hook.
If the user wants async review (close the session, come back later), they should use hive todo add --uri "review://<path>" instead — that's a different workflow and not what this skill is for.