Deliver a Jira ticket through plan approval, implementation, PR creation, and Greptile review.
npx skills add https://github.com/Omniloy/agent-skills --skill ship-omniloy
Please help me install this Agent Skill. Skill: ship Source: https://github.com/Omniloy/agent-skills/tree/main/skills/ship Command: npx skills add https://github.com/Omniloy/agent-skills --skill ship-omniloy
The ship Skill turns a single ticket or idea into a complete delivery flow, removing the manual coordination overhead of gathering context, approving a plan, opening a PR, and chasing review comments.
Ask the ship skill to take a single ticket or idea, close the gaps, get your plan approved, and then deliver it end to end.
High-intent search queries and answers about installing and using this skill.
You can automate Jira ticket delivery entirely hands-free by using the ship Skill to gather context, secure plan approval, implement the code, open a pull request, and drive Greptile code review to a 5/5 rating without manual follow-up.
An autonomous delivery loop takes a single issue from discovery through implementation and review without manual babysitting. It front-loads information gathering, requires explicit plan approval, implements the code, and drives Greptile review toward a 5/5 rating before finishing with a visual recap.
Yes, Greptile can drive iterative code review resolution on GitHub pull requests. The ship Skill uses a Greptile review loop to autonomously address feedback and achieve a 5/5 review score before publishing a final visual recap linked from the PR.
Yes, autonomous ticket delivery works with Jira issue tracking and GitHub repositories. The workflow detects your repository profile, updates or creates Jira tickets, and opens a GitHub pull request against the correct integration branch to complete the delivery.
The best way to ensure hard-to-reverse implementation choices are approved is through a plan approval gate. The ship Skill generates a visual plan that pins critical decisions and requires explicit approval before writing any code or opening a pull request.
You should avoid an autonomous delivery workflow for pull requests when a ticket lacks sufficient context for front-loaded discovery, or when a project bypasses the plan approval gate. The process requires Jira-backed, issue-driven delivery and explicit plan approval before implementation.
NexusSemaMap PRD, architecture, epics, and UX references to surface gaps and produce a prioritized remediation plan.
eugenelimCoordinate Jira defect handling from intake to pull request and tracker update.
roach88Automate pull request reviews by monitoring Greptile, fixing issues, and merging approved PRs.
euxxFetch and summarize GitHub pull request review comments for a branch.
