jira-defect-orchestrator skillA
jira-defect-orchestrator is agent-read markdown (skill) from minleev5/devkeel: 独立编排 Jira 缺陷的取证、修复、验证、回填与 MR 交付，按决策风险确认。适用于用户提供 Jira URL 或 issue key，要求结合运行日志、配置、只读业务数据和代码证据处理生产或测试环境缺陷；普通无 Jira 上下文的调试不使用。.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Jira Defect Orchestrator
## 目标与边界
把 Jira intake、运行态取证、代码根因、修复验证和交付串成一条可审计的证据闭环，并在关键决策点把控制权交给开发者。
本 Skill 独立负责 Jira 阶段、门禁、评论和状态同步，不依赖其他 Jira 编排 Skill。按需配合：
- 项目已配置的部署与日志工具：读取指定环境的应用、Pod 和历史日志。
- 项目已配置的 Apollo 读取工具：读取同一环境的配置；项目未接入时记录后跳过。
- 目标子项目的调试、实现和测试 Skill：定位代码、实施修复并验证。
- `commit`：仅在用户明确授权提交、push 或创建 MR 后使用。
普通调试没有 Jira URL 或 issue key 时，改用项目调试 Skill；不要为了使用本流程创建 issue。
## 开始前
1. 读取仓库根 `AGENTS.md` 和目标子项目的 `AGENTS.md`；代码、测试和交付只发生在受影响子仓库。
2. 检查项目根 `.jira.yml`，至少包含 `server`、`project`、`component`；需要状态同步时还要有 `transitions.in_progress` 和 `transitions.done`。配置值是目标 status 名，不是 transition action。
3. 依次执行 `command -v jira` 和 `jira me`。任一失败都停止 Jira 流程，并按 [Jira CLI 操作手册](references/jira-cli-capabilities.md) 给出最小修复指引。
4. 有 issue key 时直接查看该 issue；只有没有 key 时才在 `.jira.yml` 限定的 project/component 内查询候选。
## 主流程
```text
setup → intake → triage → investigation → G1
→ [e2e-repro] → fix-plan → G2 → implementation
→ verification → G4 → closure → G5 → done
```
| 阶段 | 必须形成的结果 | 停止条件 |
| --- | --- | --- |
| intake / triage | issue、复现、绝对时间、owner、严重度、证据缺口 | 输入不足以定位环境或现象 |
| investigation | 触发条件、实际路径、错误机制、影响和证据强度 | `G1` 存在会改变修复方向的证据缺口，且无法自主补齐 |
…Read the whole file at its exact version.
How to install
mdr add minleev5/devkeel/jira-defect-orchestrator@v1.3.2mdr add minleev5/devkeel/jira-defect-orchestrator@sha256:9979180ffb728469Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_lmwiwrgi4s7y267l)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.3.2 latest | 2026-09-24 | 8bc6bbc | 9,068 B | A | view · diff |
| v1.3.1 | 2026-09-22 | 123429c | 9,068 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 (9068 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
minleev5/devkeel · 3 stars · license MIT · pushed 2026-09-24 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_lmwiwrgi4s7y267l GET https://markdownregistry.com/api/v1/resolve?ref=minleev5/devkeel/jira-defect-orchestrator GET https://markdownregistry.com/api/v1/blob/9979180ffb72846909de347e83f25557cd3a49361b47d364862128ca5b8ecbe9
Your agent 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.