jira-defect-flow SKILL.md skillA
jira-defect-flow from eugenelim/agent-ready-repo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eugenelim/agent-ready-repo/jira-defect-flow@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eugenelim/agent-ready-repo
- Path
packs/atlassian/.apm/skills/jira-defect-flow/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0, committed Aug 29, 2026
- First version recorded
- May 25, 2026
- Size
- 14,314 bytes
- Repository stars
- 28
- License
- Apache-2.0
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 9** ("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.
## Output rendering
<!-- agentbundle:output-rendering:start -->
…Read the whole file at its exact version.
How to install
mdr add eugenelim/agent-ready-repo/jira-defect-flow@sha256:7d3f74d26889e125The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_tfdgey2t64hvrcph)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 25, 2026 and Aug 29, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-29 | fd59e28 | 14,314 B | A | view · diff |
| v1.0 | 2026-07-27 | 7ba66d5 | 11,759 B | A | view · diff |
| v1.0 | 2026-06-14 | e743b1d | 11,549 B | A | view · diff |
| v1.0 | 2026-05-27 | 388da16 | 11,549 B | A | view · diff |
| v1.0 | 2026-05-25 | 8e66005 | 11,551 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14314 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
eugenelim/agent-ready-repo · 28 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tfdgey2t64hvrcph GET https://markdownregistry.com/api/v1/resolve?ref=eugenelim/agent-ready-repo/jira-defect-flow GET https://markdownregistry.com/api/v1/blob/7d3f74d26889e125a2dea18659dbc646fdf5193d4c8be46e9dd6fcc3fa1aa088
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.