Omniloy
Official@omniloy
Offers structured engineering lifecycle management by integrating Jira issue tracking with GitHub repository code review and implementation planning.
Agent Skills by Omniloy
Showing 10 vetted skills indexed across 1 GitHub repositories.
visual-recap
Convert Git diffs into interactive visual recap documents for review.
agent-eval-api
Orchestrate Omniloy agent evaluation runs from resource discovery to result retrieval.
jira-action-plan
Convert a Jira issue into an approval-gated implementation plan with repo inspection.
live-testing-plan
Extract acceptance criteria and map tests to changed code for Jira issues.
create-jira-work-items
Create Jira feature, development task, and verification issues with duplicate checks.
prd-to-issues
Convert PRDs into structured GitHub issue plans with HTML review.
review-pr
Resolve GitHub pull request review comments with fixes and re-review requests.
greptile-resolve
Verify Greptile pull request comments against repository code and classify them.
ship
Deliver a Jira ticket through plan approval, implementation, PR creation, and Greptile review.
epic-loop
Orchestrate GitHub Milestones, Epics, and sub-issues into merged code with review gating.
Frequently Asked Questions About Omniloy
FAQPage SchemaWhat specific engineering tasks does Omniloy enable?▼
Omniloy enables the conversion of product requirements into actionable Jira issues, the generation of interactive visual recaps for code diffs, and the orchestration of pull request reviews. It facilitates end-to-end delivery by linking Jira project management directly to repository implementation and verification.
Which personas benefit most from using Omniloy?▼
Engineering managers, technical leads, and software developers benefit from Omniloy. It is designed for teams requiring rigorous gating between Jira project planning, repository implementation, and pull request verification to ensure high-quality code delivery and alignment with product requirements.
What are the prerequisites for implementing Omniloy?▼
Implementation requires active Jira and GitHub accounts with appropriate permissions for issue creation and repository access. Users must configure the integration to allow the system to perform repository inspections, pull request modifications, and milestone management within their existing development environment.