Add triage-rt-board skill and improve triage-rt regression baseline#6477
Add triage-rt-board skill and improve triage-rt regression baseline#6477
Conversation
Add a new board-level triage skill that orchestrates /triage-rt across all active tickets on a CRT/RTI regression board, caches individual reports, cross-references related tickets, and produces a prioritised board summary with fix/defer determinations and assignee workload. Also fix triage-rt regression analysis to compare against the previous release branch (the currently live version) rather than just origin/latest, which missed the majority of changes users experience.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| - Exact duplicates (same root cause) | ||
| - Related tickets (same area, different symptom) | ||
| - Recently resolved tickets that may already fix this | ||
|
|
||
| If duplicates are found, note whether they're in the current release scope (fix version matches the release branch) or not. | ||
|
|
||
| ## Step 6: Identify Suggested Assignee | ||
|
|
||
| Determine who is best placed to fix the issue based on code authorship. | ||
|
|
||
| ### Approach | ||
|
|
||
| 1. **Check authors since the previous release**: If the regression analysis (Step 3) identified commits that likely introduced the issue, the author of those commits is the strongest candidate — they have the freshest context on the changed code. | ||
|
|
||
| ``` | ||
| git log --format='%an' <baseline>..HEAD -- <relevant-file-paths> | sort | uniq -c | sort -rn |
There was a problem hiding this comment.
Step 5 uses project = AG AND component = Charts in both search queries, regardless of whether the ticket being triaged is Charts (CRT) or Grid (RTI). For Grid triage this will systematically miss Grid duplicates/related tickets, causing false "None found" results and potentially wrong release recommendations. The query needs to be parameterised by detected product/component (Charts vs Grid).
| | # | Ticket | Title | Category | Regression | Risk | Scope | Assignee | | ||
| | --- | ------ | ----- | -------- | ---------- | ---- | ----- | -------- | | ||
|
|
There was a problem hiding this comment.
ℹ️ [P2] Template uses non-schema risk value Zero
The board summary example row uses Risk | Zero, but the documented schema elsewhere is Low | Medium | High | N/A. This inconsistency can leak into cached reports or summaries and break downstream parsing/aggregation assumptions.
|
❌ Codex review complete; 2 issues found (P0: 0 | P1: 1 | P2: 1 | P3: 0) View full reviewAdd triage-rt-board skill and improve triage-rt regression baselinePR: #6477 SummaryThis PR introduces two new release-triage skills and a scope/risk reference guide, with stronger guidance around using the previous release as the regression baseline. The overall structure is solid, but one product-selection bug in JIRA duplicate search can produce incorrect triage outcomes for Grid tickets. FindingsP0: 0 | P1: 1 | P2: 1 | P3: 0 2 inline comments posted. VerdictAssessment: incorrect The skills are well-structured, but the hardcoded Charts duplicate-search query creates a functional correctness issue for Grid triage and can directly affect decision quality. Required Actions:
|
… category-based ordering Priority is now: Library regressions > Library core non-regressions > Library non-core non-regressions > Docs & examples > Website. Feasibility (fix/defer) is applied as a filter within each category rather than defining the tier itself.
The Atlassian MCP tools silently drop rank field updates via editJiraIssue, requiring the dedicated Agile REST API endpoint. Add Step 7 to triage-rt-board for applying board prioritisation via curl, including auth verification and token setup guidance. Add ranking reference to the jira skill documenting the instance-specific rank field ID, API patterns, and MCP limitations.
Sub-agents were producing shallow reports (3 short paragraphs) compared to direct /triage-rt invocations (full multi-section analysis). Root cause: sub-agents read the skill file as loose instructions and compressed steps. Adds mandatory tool-call checklist, required report sections, 200-word minimum threshold, and a post-wave validation gate to catch thin reports.
alantreadway
force-pushed
the
bls/triage-rt-board-skill
branch
from
b6595aa to
e888171
Compare
Expand the shared code-quality guide with a "Design and Modularity" section (single responsibility, small functions, composition, dependency direction, file organisation, minimal surface, pure functions). Add a pre-commit self-review checklist to the ag-charts root rule so AI tools verify quality before running lint/format/type-check. Update SYNC-LOG with migration notes.
2 participants
Summary
/triage-rt-boardskill that orchestrates board-level triage across all active CRT/RTI regression tickets, producing a prioritised summary with fix/defer determinations, cross-references, and assignee workload/triage-rtregression analysis to compare against the previous release branch rather than justorigin/latest, capturing the full delta since the last shipped versionscope-risk.mdreference for library impact assessmentTest plan
origin/b13.1.0)