ship

Automate task review, testing, and commit for repository closure.

16|2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Kibertum/tausik-core --skill ship-kibertum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Kibertum/tausik-core/tree/main/agents/skills/ship
Command: npx skills add https://github.com/Kibertum/tausik-core --skill ship-kibertum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship It unifies the end-to-end closure of a completed task by performing review, testing, gate checks, and commit in one streamlined operation, ensuring nothing is missed before closing.

Core Features & Use Cases

  • End-to-end shipping: automatically locate the active task, load its context (AC, plan, goal), verify plan completion, run full review and tests, verify acceptance criteria, and perform a final commit and close.
  • Gatekeeping: auto-escalates deep review for high-risk diffs and ensures security and quality gates are satisfied before closing.
  • Safe close: ties the commit to the task slug and marks the task as done only after successful AC verification and commit.

Quick Start

Say "ship it" to trigger the full closure workflow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate task closure with code review and commit in one step?

You can automate task closure by triggering a workflow that locates the active task, verifies plan completion, runs full review and tests, verifies acceptance criteria, and performs a final commit before closing.

What happens if acceptance criteria are not met during automated commit?

If acceptance criteria are not met, the automated commit will not execute. The workflow ensures gates like review, tests, and acceptance criteria verification are satisfied before performing the final commit and marking the task as done.

Can I run automated tests and security gates before pushing to a repository?

Yes, the workflow runs full reviews and tests, auto-escalating deep review for high-risk diffs, and ensures security and quality gates are satisfied before performing the final commit and pushing to the repository.

Does the workflow require an active task to run a final commit?

Yes, an active task is required. The workflow automatically locates the active task, loads its context including acceptance criteria, plan, and goal, and ties the final commit to the task slug before marking it as done.

What is the best way to ensure no quality gates are missed before closing a task?

The best way is using an end-to-end workflow that verifies plan completion, runs reviews, executes tests, and verifies acceptance criteria before safely closing the task with a tied commit.

Are there limitations to automated task closure for high-risk code diffs?

There are no strict limitations, but the workflow auto-escalates deep review for high-risk diffs. It ensures security and quality gates are satisfied before performing the final commit and closing the task.