open-horizon-labs/skills
Overview
This skill optimizes the final step of execution: getting merged code into users' hands. It maps the delivery path, surfaces the delivery-path tax (friction), and runs or guides the actions needed to deploy and verify changes. The goal is fast, reliable delivery so completed work actually delivers value.
How this skill works
It inspects the delivery workflow from merge to install and identifies where time is lost: review queues, merge conflicts, gates, approvals, and deploy mechanics. When CI/CD context is available it references pipeline definitions, can trigger or label workflows, monitor runs, and verify deployments. When pipeline access is absent it produces a clear manual checklist, commands to run, and verification steps. It produces a structured ship report summarizing actions, verification, and recommendations.
When to use it
- Execution is complete and code is reviewed and tested
- You need to get merged changes deployed to staging or production
- Delivery feels slow despite work being finished
- Approvals, scans, or CI gates are blocking progress
- You want to automate or streamline the path from merge to install
Best practices
- Map the full delivery path and name each owner before taking action
- Measure delivery-path tax (time per step) to prioritize fixes
- Automate low-risk approvals and parallelize static checks where safe
- Trigger and monitor CI/CD runs when possible; otherwise provide exact manual commands
- Verify deploys with quick, ad-hoc checks before declaring success
Example use cases
- Merge is approved and you need an automated prod deploy via CI/CD
- Several PRs are stalled—analyze review/scan bottlenecks and recommend fixes
- No CI for a device firmware update—provide step-by-step flash and verification commands
- Improve throughput by suggesting gating changes: parallel scans, fewer approvers for UI-only changes
- Create a short ship report and persist deployment status to a session file for later review
FAQ
A Ship Report that lists what was shipped, the target, the path taken, delivery friction, actions performed, verification checklist, and recommendations.
Can this trigger pipelines automatically?
Yes, when CI/CD configuration and integration access are available it can reference workflows, trigger runs, and monitor their status.
What if I have no pipeline access?
It produces an explicit manual deployment checklist, command examples, verification steps, and a final status report you can follow or share.
2 skills
This skill streamlines delivering completed code to users by identifying delivery friction and orchestrating automated, reliable ship workflows.
This skill provides a second opinion before committing by reviewing intent against execution, catching drift, and guiding next steps.
