skills.rest
oobagi
oobagiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

polish

Chain /simplify, /harden, /test, and /ship steps with stop-on-failure.

Updated Aug 23, 2026
Search Tags:#automation#pipeline#ci-cd#quality-assurance#polish#workflow-orchestration#ad-hoc-work
One-click install
npx skills add https://github.com/oobagi/jflow --skill polish-oobagi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/oobagi/jflow/tree/main/skills/polish
Command: npx skills add https://github.com/oobagi/jflow --skill polish-oobagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-implementation polish pipeline that automatically chains the /simplify → /harden → /test → /ship steps, reducing manual orchestration and speeding up shipping of ad-hoc work.

Core Features & Use Cases

  • End-to-end workflow: Chains /simplify → /harden → /test → /ship in sequence, stopping on first failure.
  • Flexible control: Supports dry-run and no-ship modes, and selective stepping via skip-simplify or skip-harden.
  • Scale to dynamic work: Ideal for rapid hardening of on-the-fly changes, QA passes, and preparing patches for shipping.

Quick Start

Run the polish skill to automatically execute the simplify, harden, test, and ship pipeline on your current changes.

Frequently Asked Questions about polish

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

FAQPage Schema
How do I automate post-build polish and hardening for ad-hoc code changes?▼

Automate post-build polish by chaining a guided pipeline that sequentially applies simplify, harden, test, and ship steps to your code changes. This workflow orchestration reduces manual steps and stops on the first failure to ensure quality assurance before shipping.

Can I run a dry-run or preview validation without shipping code changes?▼

Yes, you can run a dry-run or use the no-ship mode to preview validation and hardening. These options execute the quality assurance pipeline and prepare patches while halting before the final shipping step to safely review changes.

What is the standard CI-CD workflow sequence for rapid code hardening?▼

The standard CI-CD workflow sequence for rapid hardening is simplify, followed by harden, then test, and finally ship. This ordered step execution ensures progressive quality assurance and validation across development workflows before deployment.

Does the polish pipeline support skipping specific hardening or simplification steps?▼

Yes, the polish pipeline supports selective stepping via skip-simplify or skip-harden options. This allows you to bypass specific phases in the workflow orchestration while still running the remaining validation and shipping steps in sequence.

What happens when a test or hardening step fails during automated pipeline execution?▼

When a step fails during automated pipeline execution, the stop-on-failure behavior immediately halts the sequence. This prevents subsequent execution and ensures no broken changes advance to the final shipping phase without passing validation.

Related Skills

Explore More Software Engineering Skills→
MrAlexisCordMrAlexisCord

requesting-code-review

Dispatch a specialized subagent to review code changes against requirements.

Community
Intermediate
patricio0312revpatricio0312rev
5

caching-strategy-optimizer

Apply caching strategies to reduce CI/CD pipeline runtimes.

Community
Intermediate
first-flukefirst-fluke
1.2k

ultrawork

Orchestrate a 5-phase, 17-step development workflow with phase-gate loops.

Official
Advanced
DangQuangSEDangQuangSE
19

ck:quality

Evaluate code against an Engineering Quality Contract for architectural and domain integrity.

Community
Advanced