Skip to content

1.1: JSON rubrics, built-in ticket-quality rubric and issue mappers - #2

Merged
davidnmbond merged 8 commits into
mainfrom
feature/rubrics
Oct 14, 2026
Merged

davidnmbond merged 8 commits into
mainfrom
feature/rubrics

Conversation

@davidnmbond

Copy link
Copy Markdown
Contributor

Adds rubrics so Yoda's skills and the QA Dashboard can share one definition of ticket quality.

What's new

  • AssessmentRubric: whole configurations as JSON, validated at construction.
  • TieredAssessment, conditions and measures over text sources that can narrow to a headed section (Jira wiki or Markdown).
  • Applicability (AppliesWhen, NotApplicable outcome, renormalised scores), category weights, score caps, grade bands, classifications and flags, reported as IAssessmentResult.Overall.
  • Recommendations, and AssessmentReport (flat, serializable).
  • BuiltInRubrics.PanoramicDataTicketQuality.
  • NormalizedIssue with Jira (v2 and v3/ADF), GitHub and ServiceNow mappers, plus IssueText helpers.

Everything is additive: 1.0 code compiles and behaves as before.

Parity

The built-in rubric matches IssueQualityCore.ps1 on score, grade, findings, recommendations, flags and automation type:

  • all 74 of its test fixtures, committed as golden tests;
  • 320 real Jira tickets, not committed because they are customer data.

Quality

  • 815 tests pass.
  • 100% line coverage of the library and 99.4% branch coverage.
  • README, DESIGN and CHANGELOG updated; version 1.1.

🤖 Generated with Claude Code

davidnmbond and others added 7 commits October 13, 2026 17:36
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pplicability, caps, grades, classifications

- IssueText: port of Yoda's section reader, criteria headings and placeholder test.
- Rules: EvaluationContext with cached text and named conditions; measures and conditions.
- TieredAssessment: first matching tier scores, with findings and recommendations.
- AppliesWhen on assessments and categories; not-applicable work is left out of scores.
- Category weights; score caps; grade bands; classifications; overall verdict on results.
- Assessment outcome and recommendation on results.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rs (Jira REST/ADF, GitHub, ServiceNow)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…'s engine

Parity with PanoramicData.Skills IssueQualityCore.ps1, checked field by field (score,
grade, findings in order, recommendations, flags, automation type, mandatory caps and
every factor score): 75/75 of Yoda's own test fixtures (one differs only because that
test temporarily changes two weights) and 320/320 real Jira tickets (MS bugs, epics,
stories and tasks, PS tickets, change requests), through both Yoda's conversion and
JiraIssueMapper.

Engine additions the port needed: {$.path~pattern} and {measure:text} placeholders,
placeholders in not-applicable explanations, empty findings for recommend-only tiers,
and NormalizedIssue.Platform.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… generated code from coverage

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…lines)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codacy-production

codacy-production Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 516 complexity · 2 duplication

Metric Results
Complexity 516
Duplication 2

View in Codacy

🟢 Coverage 100.00% diff coverage · +0.00% coverage variation

Metric Results
Coverage variation ✅ +0.00% coverage variation (-1.00%)
Diff coverage ✅ 100.00% diff coverage

View coverage diff in Codacy

Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (f5c8a2e) 1138 1138 100.00%
Head commit (b309f35) 1954 (+816) 1954 (+816) 100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#2) 885 885 100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@davidnmbond
davidnmbond merged commit 490b78f into main Oct 14, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant