jira-defect-flowlisted

Use this skill when the user points at a Jira defect and asks you to handle it end-to-end -- "fix PROJ-123", "work this bug ticket", "diagnose and ship a fix for this defect". The skill pulls the ticket via the `jira` skill, hands the actual fix to the `bug-fix` skill (reproduction-first, root-cause, minimum-diff, regression-test), opens a PR whose body links back to Jira, and comments + transitions the ticket. By default it stops at PR-opened; runs a dev-deploy step only if the consumer repo provides one. Do NOT use for stories, tasks, or feature work -- those go through `new-spec`.
eugenelim/agent-ready-repo · ★ 7 · Code & Development · score 81

Install: claude install-skill eugenelim/agent-ready-repo

# Skill: jira-defect-flow This is choreography, not invention. It composes three things that already exist: - **`jira` skill** (sibling in this pack) — all Jira reads, comments, transitions, attachments. You never write a raw Jira REST call here. - **`bug-fix` skill** (shipped by the host repo; resolved by name through the harness) — reproduction, failing test, root-cause identification, minimum fix, regression test, commit-body-explains-why, and tracker loopback. This skill does **not** re-explain that discipline; invoke `bug-fix` and follow it. **Stages 6–7 below are the Jira-specific mechanism for `bug-fix` step 8** ("loop back to the tracker") — not a separate obligation. - **Reviewer subagents** (`adversarial-reviewer`, plus `security-reviewer` / `quality-engineer` when the diff warrants) — already wired into the consumer repo's work-loop. If you find yourself writing a Jira REST call, a reproduction recipe, or a root-cause checklist inside this skill, stop — the right place is one of the three above. ## Cross-skill invocation — name, not path This skill names sibling skills (`jira`, `bug-fix`) and subagents (`adversarial-reviewer`, `security-reviewer`, `quality-engineer`) **by their `name:` field, never by path**. Install locations vary by IDE and scope, and skills can be renamed at install time. Path coupling silently breaks every alternative layout. The contract: when this skill says *"via the `jira` skill: `get-issue $KEY ...`"*, the agent u