be-jira-auto

Orchestrates Jira tickets through the full backend scaffold, TDD, verify, review, and commit pipeline.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill be-jira-auto-ohmyhotelco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: be-jira-auto
Source: https://github.com/ohmyhotelco/hare-cc-plugins/tree/main/backend-webflux-plugin/skills/be-jira-auto
Command: npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill be-jira-auto-ohmyhotelco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually running each backend pipeline step (scaffold, implement, verify, review, fix, commit) for every Jira ticket is repetitive and error-prone. This Skill reads a Jira issue, derives the implementation inputs, and drives the entire be-crud → be-code → be-verify → be-review → be-fix → be-commit pipeline automatically. ## Core Features & Use Cases - Jira-driven orchestration: Fetches a ticket via a discovered Jira MCP tool, extracts the stated Technical Approach when present, or drafts a Proposed Solution and stops for user confirmation when not. - Tiered review gating: Classifies tickets as easy, normal, or extreme to scale the security review gate, while never skipping verification or code review. - Unattended pipeline execution: Resolves all interactive prompts upfront (domain, data profile, fields, scenarios) and delegates each step to the plugin's own be-* skills via the Skill tool. - Use Case: Run /backend-webflux-plugin:be-jira-auto OMH-1234 to have the ticket's new entity scaffolded, implemented with TDD, verified, reviewed, and committed on a freshly created branch without manual step-by-step invocation. ## Quick Start Invoke the skill with a Jira issue key such as /backend-webflux-plugin:be-jira-auto OMH-1234 to run the full backend pipeline for that ticket.

Frequently Asked Questions about be-jira-auto

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

FAQPage Schema
How do I implement a Jira ticket automatically in a Spring WebFlux project?▼

Invoke the skill with the Jira issue key, for example /backend-webflux-plugin:be-jira-auto OMH-1234. It fetches the ticket via a Jira MCP tool, derives the design, and runs the full scaffold, TDD, verify, review, and commit pipeline unattended.

What happens when a Jira ticket has no technical approach written?▼

The skill scans the existing codebase, drafts a Proposed Solution from the summary and acceptance criteria, then stops with NEEDS-INPUT so the user can confirm or correct it. Implementation only starts after confirmation is passed back via the notes parameter.

Does the pipeline ever skip verification or code review?▼

No. Verification and review always run regardless of ticket size. The easy/normal/extreme tier only controls whether the parallel security gate runs, and security-sensitive tickets always force the security review.

Why does the skill stop with NEEDS-INPUT during a run?▼

It stops when input cannot be resolved unattended: a missing Jira MCP tool, multiple Jira sources, gaps in the ticket's stated approach, a dirty working tree from other work, critical security findings, or repeated fix failures. The user resolves the issue and re-invokes.

Can the skill push branches or create pull requests?▼

No. The pipeline deliberately ends at the commit step. Pushing, opening pull requests, and transitioning the Jira issue are manual decisions left to the user outside this skill.