skills.rest
udecode
udecodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

slate-ar-ship

Runs finalization previews, proof gates, and autoreview before committing Slate v2 AR work.

16.5k|997|Updated Dec 2, 2019
Search Tags:#Git#finalization#pre-commit#Automation#commit workflow#Code review#Slate
One-click install
npx skills add https://github.com/udecode/plate --skill slate-ar-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: slate-ar-ship
Source: https://github.com/udecode/plate/tree/main/.agents/skills/slate-ar-ship
Command: npx skills add https://github.com/udecode/plate --skill slate-ar-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preparing Slate v2 autoresearch work for review or commit involves many manual steps—finalization previews, choosing the right review unit, running proof gates, and pre-commit review—which are easy to skip or run in the wrong order.

Core Features & Use Cases

  • One-Command Ship Flow: Runs finalization preview, picks the honest review unit (kept AR packets vs current tree), and reports readiness without requiring parameters.
  • Pre-Commit Review Path: When a dirty tree blocks finalization, runs focused proof gates and autoreview on the uncommitted diff before any commit.
  • Approval-Gated Commits: Pauses with a READY TO COMMIT prompt and only commits after explicit user confirmation, never pushing or opening PRs without approval.
  • Use Case: After a Slate v2 editing session with uncommitted changes, invoke the skill to get a readiness report, automated review of the current tree, and a clean commit once you confirm.

Quick Start

Ask the assistant to run slate-ar-ship to make the current Slate v2 work reviewable and ready to commit.

Frequently Asked Questions about slate-ar-ship

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

FAQPage Schema
How do I make Slate v2 autoresearch work ready for review?▼

Run slate-ar-ship with no arguments. It runs a finalization preview, decides whether kept AR packets or the current tree is the honest review unit, executes proof gates and autoreview, then pauses for commit approval.

How to review uncommitted changes before committing in a git workflow?▼

The skill runs autoreview against the uncommitted current-tree diff plus focused proof gates when editor behavior changed. Only after review is clean does it print READY TO COMMIT and wait for your confirmation.

Does slate-ar-ship commit or push automatically?▼

No. Plain invocation only runs non-mutating readiness work like previews, gates, and autoreview. Committing requires explicit confirmation after the READY TO COMMIT pause, and push or PR creation needs separate explicit approval.

What happens when the working tree is dirty during finalization?▼

Instead of stopping, the skill runs a pre-commit review path: focused gates, autoreview on the uncommitted diff, and fixes for accepted P0/P1 findings. Session artifacts are excluded from the commit and stashed if needed.

When should I use current-tree finalization instead of kept AR packets?▼

Use current-tree finalization when useful work was bundled or corrected outside kept AR packets, or when the branch has many unkept commits that belong in the review. It is a preview-only readiness step, not a commit.

Related Skills

Explore More Software Engineering Skills→
nq-rdlnq-rdl

charm-tui

Guide building terminal user interfaces in Go with Charm v2 libraries.

Official
Advanced
yusaduymazyusaduymaz

gsd-ship

Push verified branches and open pull requests for merge tracking.

Community
Advanced
terakoya76terakoya76

review

Automate code review of uncommitted git changes with a reviewer subagent.

Community
Basic
gmcabritagmcabrita
6

autoresearch-finalize

Convert autoresearch sessions into independent branches from the merge-base.

Community
Advanced