Draft Review with the CLI
Purpose: Use the Commentary CLI for live collaborative review of local text artifacts.
Use it when: Use when local Markdown, MDX, HTML, or text needs a hosted human review.
Install
Section titled “Install”Check out the published v0.6.2 tag of the Commentary Skills repository, then copy the complete skills/commentary-draft-review/ folder into the skills directory for your compatible SKILL.md agent. Preserve references and metadata. Restart or refresh the harness if it loads skills at startup.
Invoke
Section titled “Invoke”Copy this request into a compatible agent:
Use `commentary-draft-review` to create a Draft Review for `./docs/release-plan.md`, share it only if I ask, and wait for reviewer comments. Keep the local file authoritative; after feedback, sync a new revision and report its review link.Expected result: The agent returns a hosted review link and the next actionable comment or bounded wait state; edits remain local until explicitly synced.
Workflow
Section titled “Workflow”Authenticate with the CLI, create a Draft Review from local files, share only when requested, read comments, edit locally, sync a new immutable revision, and resolve threads with proper approval.
Environment and limits
Section titled “Environment and limits”Read the published v0.6.2 SKILL.md and its referenced files for the exact transport, scopes, target, and environment settings; those instructions are authoritative for this skill. For transport setup, see CLI, MCP, and Developer access. Never store credentials in the skill folder or send them to a renderer. Local files remain the source of truth unless the user explicitly asks to pull reviewed content. CLI authentication is separate from project metadata; no Git commits or PRs are created.