slate-ar-finalize

Runs preview-only finalization for Slate v2 Autoresearch sessions with explicit review-branch approval gating.

16.5k|997|Updated Dec 2, 2019
One-click install
npx skills add https://github.com/udecode/plate --skill slate-ar-finalize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slate-ar-finalize
Source: https://github.com/udecode/plate/tree/main/.agents/skills/slate-ar-finalize
Command: npx skills add https://github.com/udecode/plate --skill slate-ar-finalize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning kept Slate Autoresearch work into reviewable output is risky: accidental branch creation, commits, or pushes can happen when finalization commands are ambiguous. This Skill enforces a safe, preview-first finalization contract so nothing mutates the repository without explicit approval.

Core Features & Use Cases

  • Preview-Only Finalization: Runs finalize-preview --cwd .tmp/slate-v2 by default and treats the output as read-only evidence.
  • Readiness Reporting: Reports kept evidence, excluded session artifacts, dirty-tree warnings, semantic-safety warnings, overlap warnings, unkept commits, and final-tree coverage.
  • Strict Mutation Gating: Review branches are opt-in only; the user must explicitly say "review branches" or equivalent wording, and plain "go", "ok", "ship", or "next" never approves branch creation.
  • Use Case: After a Slate v2 Autoresearch session, ask for finalization to get a read-only readiness report, then explicitly request review branches only when you are ready to create autoresearch-review/* branches.

Quick Start

Ask the assistant to finalize the Slate v2 Autoresearch session in preview mode and report readiness before creating any review branches.

Frequently Asked Questions about slate-ar-finalize

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

FAQPage Schema
How do I finalize a Slate Autoresearch session safely?

Run the finalization in preview mode first, which executes finalize-preview against .tmp/slate-v2 as read-only evidence. Review the reported kept evidence and warnings, then explicitly request review branches only when ready.

What does the Slate AR finalization preview report include?

The preview reports kept evidence, excluded session artifacts, dirty-tree warnings, semantic-safety warnings, overlap warnings, unkept commits, and final-tree coverage. All of this is read-only and creates no branches or commits.

Does saying "ship" or "finalize" create review branches?

No. Plain confirmations like "go", "ok", "continue", "next", "ship", "finalize", or "current-tree" only continue work and report readiness. Branch creation requires explicit wording such as "review branches" or "create review branches" in the current turn.

When should I use finalize-current-tree instead of finalize-preview?

Use finalize-current-tree as a read-only readiness preview when the current working tree itself is the intended review unit, rather than the kept Autoresearch session state. Both modes are non-mutating.

Can this skill commit, push, or open pull requests automatically?

No. It never creates branches, cleans files, commits, pushes, or opens PRs without exact user approval for that specific mutation. The default and preview flows are strictly read-only.