菜单
Check known issue status for a release version. Shows which known issues are still open (document in Known Issues) and which are resolved (move to Fixed Issues or remove). Use when asked to check known issues, audit release notes known issues, or find resolved known issues for a version.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Documentation workflow orchestrator. Reads the step list from .agent_workspace/docs-workflow.yaml (or the plugin default). Runs steps sequentially, manages progress state, handles iteration and confirmation gates. Claude is the orchestrator — the YAML is a step list, not a workflow engine.
Write documentation from a documentation plan. Dispatches the docs-writer agent. Supports AsciiDoc (default) and MkDocs formats. Default placement is UPDATE-IN-PLACE; use --draft for staging area. Also supports fix mode for applying technical review corrections.
Score documentation quality and intent alignment using LLM judge agents (Opus). Dispatches two judge agents in parallel (doc_quality, intent_alignment), extracts specific gaps from AC coverage analysis, and cross-references against scope-req-audit evidence. Produces pass/fail gate with actionable gap list. Iteration logic is owned by the orchestrator, not this skill.
Run code-learner analysis on a source repository for the docs orchestrator workflow. Dispatches a subagent to run learn-code, keeping the heavy orchestration out of the main context. Produces ONBOARDING.md, module registry, per-module summaries, and cross-module relationship data.
Classify JIRA requirements by code evidence status before planning. Uses learn-code analysis data and source code inspection to determine if each requirement is grounded, partial, or absent. Fans out one subagent per requirement for isolated classification. Prevents hallucinated documentation for unimplemented features and surfaces gaps for implemented ones. Conditional on has_source_repo.
Technical accuracy review with optional code-learner claim validation. Iteration logic owned by the orchestrator.
| name | rn-known-issues |
| description | Check known issue status for a release version. Shows which known issues are still open (document in Known Issues) and which are resolved (move to Fixed Issues or remove). Use when asked to check known issues, audit release notes known issues, or find resolved known issues for a version. |
| allowed-tools | Read, Bash, Grep, Glob |
Audit known issues for a release version. Produces a categorized report showing which known issues remain open and which have been resolved since the previous release.
$1 — Target fix version (required, e.g., rhoai-3.4.1)--project — Jira project key (default: RHOAIENG)--previous — Previous GA version to check for resolved known issues (auto-inferred if not provided)When --previous is not provided, infer the previous GA version from the target:
| Target pattern | Previous GA |
|---|---|
rhoai-X.Y.Z (z-stream) | rhoai-X.Y |
rhoai-X.Y (GA) | rhoai-X.(Y-1) |
rhoai-X.Y.EAn | rhoai-X.Y |
Examples:
rhoai-3.4.1 → previous = rhoai-3.4rhoai-3.5 → previous = rhoai-3.4rhoai-3.4.2 → previous = rhoai-3.4Run these JQL queries via the Atlassian MCP (searchJiraIssuesUsingJql) with cloudId = "redhat.atlassian.net".
If the Atlassian MCP is unavailable or unauthenticated, fall back to jira-reader:
# Claude Code
uv run --script ${CLAUDE_PLUGIN_ROOT}/skills/jira-reader/scripts/jira_reader.py --jql "<JQL>" --fetch-details
# Cursor
uv run --script skills/jira-reader/scripts/jira_reader.py --jql "<JQL>" --fetch-details
project = {PROJECT} AND "Release Note Type" = "Known Issue"
AND fixVersion = "{TARGET_VERSION}"
AND statusCategory != Done
ORDER BY priority DESC, key ASC
These are active known issues — document them in the Known Issues section of the release notes.
project = {PROJECT} AND "Release Note Type" = "Known Issue"
AND fixVersion = "{TARGET_VERSION}"
AND statusCategory = Done
ORDER BY key ASC
These were found and fixed within the same release cycle. Decide whether they need a Known Issue entry (with a note that it's fixed) or can be omitted.
project = {PROJECT} AND "Release Note Type" = "Known Issue"
AND fixVersion = "{PREVIOUS_VERSION}"
AND statusCategory = Done
ORDER BY key ASC
These are resolved known issues from the prior release — candidates for:
project = {PROJECT} AND "Release Note Type" = "Known Issue"
AND fixVersion = "{PREVIOUS_VERSION}"
AND statusCategory != Done
ORDER BY priority DESC, key ASC
These remain open — they must stay in the Known Issues section.
Request these fields in each query:
summary, status, fixVersions, customfield_10785, customfield_10807, customfield_10783, resolution, priority
Field reference:
customfield_10785 — Release Note Typecustomfield_10807 — Release Note Status (Done, In Progress, Proposed, Approved)customfield_10783 — Release Note Text (ADF format)Present results as a markdown report:
# Known Issue Audit: {TARGET_VERSION}
Project: {PROJECT}
Previous version: {PREVIOUS_VERSION}
Date: {TODAY}
## Still-open known issues in {TARGET_VERSION} (document these)
| Key | Summary | Priority | RN Status |
|-----|---------|----------|-----------|
| ... | ... | ... | ... |
**Count:** N issues
## Resolved known issues in {TARGET_VERSION} (found-and-fixed same cycle)
| Key | Summary | Resolution | RN Status |
|-----|---------|------------|-----------|
| ... | ... | ... | ... |
**Count:** N issues
## Resolved from {PREVIOUS_VERSION} (move to Fixed Issues)
| Key | Summary | Resolution | RN Status | RN Text filled? |
|-----|---------|------------|-----------|-----------------|
| ... | ... | ... | ... | Yes/No |
**Count:** N issues — these can be removed from Known Issues and optionally added to Fixed Issues.
## Carry-forward from {PREVIOUS_VERSION} (still open)
| Key | Summary | Priority | Status | RN Status |
|-----|---------|----------|--------|-----------|
| ... | ... | ... | ... | ... |
**Count:** N issues — these remain in the Known Issues section.
## Summary
- New known issues to document: N
- Previously known issues now fixed: N
- Carry-forward (still open): N
- Release note text missing: N (list keys)
For each issue, check if customfield_10783 (Release Note Text) has content beyond the template skeleton (Cause:\nConsequence:\nWorkaround:\nResult:). Flag issues where the text is empty or only contains the template headings.
Z-stream audit — what's changed since the last GA?
"Check known issues for rhoai-3.4.1"
Audits rhoai-3.4.1 against the inferred previous version rhoai-3.4. Shows any new known issues in 3.4.1, which 3.4 known issues are now fixed, and which carry forward.
GA release — what resolved from the prior GA?
"Run rn-known-issues for rhoai-3.5 --project RHOAIENG"
Audits rhoai-3.5 against rhoai-3.4. Useful at GA time to see which long-standing known issues finally got fixed.
Explicit previous version — check across multiple z-streams
"Check known issues for rhoai-3.4.2 --previous rhoai-3.3"
Overrides version inference to compare against an older baseline. Useful when you want to see everything resolved since 3.3 (skipping the intermediate 3.4 GA).
Different project
"Audit known issues for rhoai-3.4.1 --project RHAIENG"
Same workflow against the Red Hat AI Engineering project instead of OpenShift AI.
Pre-release checklist
"Before we ship rhoai-3.4.1, check known issues — are any still open that should block the release?"
The agent will focus on Query 1 (still-open known issues in the target version) and flag Blocker/Critical priorities.
RHOAIENG (not RHAIENG, which is a separate project).rhoai-X.Y for GA releases, rhoai-X.Y.Z for z-stream patches.customfield_10785), not a separate field or label.