Repository navigation
Issue triage with Jev: categories, complexity 1–10, autonomous severity check, and dashboard summary cards - #3
Merged
Merged
Conversation
Categories (default list, replaceable per project), complexity 1-10 as fix effort, and an independent Jev severity check, stored as suggestions in an append-only assessments.yaml and applied only through `accept`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No human accept step: rules in code apply confident judgments to gaps and to Jev's own earlier values, never over explicit ones; uncertain answers and confident disagreements go to a triage queue that agents resolve with set. Also folds in the Fable review: non-fatal category drift, an append-only log that can't fail validation, render-time disagreement, argmax complexity, file-order ties, injectable backoff and UTC ids. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- a hand-edited Jev value is explicit and never overwritten - type is derived from category and carries no provenance - validate() keeps returning errors; validateAll() adds warnings - auto-assess on add-issue is opt-in (jev.auto_assess or --assess) - disagreements don't resurrect for an unchanged suggestion - default assess only fills gaps; --refresh revises Jev's own values - severity gate starts at 0.85; one number format; unset severity sorts last Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Eleven TDD tasks from the approved spec (revision 2.1): categories and config, schema and validation, triage policy, edits and the assessment commit, request builder, client, assess, agent CLI, STATUS.md, dashboard, docs and demo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…venance Adds the optional issue fields details, category, complexity and triage, the assessments.yaml log shape, and validateAll/store.check with warnings that never block a write. severity is no longer required. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A gap whose latest answer passes the gate (value deleted afterwards, or the category listed afterwards) no longer reports a misleading low confidence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved in conversation: four headline cards (open, fixed, coverage, hotspot), three panels (by feature, severity x status, work queue), the same numbers as a STATUS.md Summary, and table legends turned into accessible header tooltips with a print-only legend for PDF export. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The API returns `answers` keyed by question id (docs.typesafe.ai/api.md), which mapAnswers consumes; the client rejected every real response as malformed because it required an array. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add `triage [--json]`; `set <issue> category|complexity|severity|details`; add-issue takes --details/--category/--complexity, optional --severity and opt-in auto-assess (--assess/--no-assess, jev.auto_assess); `get` shows triage provenance, the latest assessment and warnings naming the issue; `validate` prints warnings. Pure formatters live in src/triage-format.mjs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Issue tables show Category and Cx with a J marker for unconfirmed Jev values, a severity/complexity/status legend, and a Triage queue section with the issue warnings under it. status and STATUS.md share one render. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Issue tables gain Category and Cx columns (unset shows an em dash, severity class "sev none"), Jev-set cells carry a "Jev 91%" tooltip, edit mode gets selects for category, complexity and severity, and a Triage queue section mirrors STATUS.md. Issue sorting moves to shared helpers in format.mjs, which also fixes the NaN ordering the dashboard had for unset severity. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The legend explains the mark, so Jev-owned cells now show it after the value, as STATUS.md does, alongside the existing confidence tooltip. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
README "Triage with Jev" section, agent guide and skill without required --severity, demo issues with categories/complexity and an illustrative assessments.yaml, and the live smoke script (npm run smoke:jev). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
--assess=false used to store the string 'false' and opted in to sending the issue to TypeSafe. Boolean flags now take true/1/false/0 after =, and anything else is a usage error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A 422 now reads 'request rejected (422): <API message>', and the 'shorten
details' hint is added only when the API message is about size, length,
tokens or being too large. Test fakes in the client, assess and CLI tests are
real Response objects, so the production text() + JSON.parse path is what runs;
the unused res.json() fallback in the client is removed, and an empty JSON
error body is no longer shown as '{}'.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hanges in the changelog Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f04db77f80
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
From the Codex review of #3: - reject a confidence outside [0, 1] while mapping each answer, so one bad response fails its own issue instead of sinking the whole batch at validate - an answer from a different model than the run's first fails that issue, so the single `model` on the assessment entry stays true for every judgment - id-keyed result maps have no prototype (and add-assessment builds `applied` with Object.fromEntries), so an issue id of `__proto__` is committed like any other instead of silently vanishing Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Issue triage with TypeSafe's Jev, plus summary cards for the dashboard. It implements the approved spec
docs/superpowers/specs/2026-10-04-issue-triage-jev-design.md(revision 2.1) through the 12-task plan indocs/superpowers/plans/.Triage data
category: one of 11 defaults, or a project's own list inqa-tracker.config.json. Each category maps totype.complexity: 1–10, meaning effort to fix.details: free-text description.severityis now optional.issue.triagerecords whether Jev set the value or someone set it on purpose. A newassessments.yamlkeeps every Jev judgment and is only ever appended to.validatenow separates errors from warnings. Changing the category list, or a stale entry in the history file, never blocks a write.validate()keeps its old contract, andvalidateAll()returns both.Autonomous triage, with no human accept step
qa-tracker assessasks Jev for category, complexity and severity. Code-side confidence gates (70% / 50% / 85%) decide what gets applied.qa-tracker triage). Agents resolve the queue withset.--dry-runprints the exact requests and needs no key. Auto-assessing new issues onadd-issueis opt-in:"jev": { "auto_assess": true }, or--assess.fetch(no new dependency), with retries for 429/529, network errors and timeouts. A 401 stops the run.Views
Why
Findings needed finer categories than the three
types, and a fix-effort estimate next to impact. Severity (impact) and status (lifecycle) were being confused. The user also wanted this to run without anyone in the loop, so agents stay autonomous: code applies Jev's judgments, and agents handle whatever the code won't apply.For reviewers
assess, and opted-inadd-issue, send anything. They send the issue title anddetails, the feature's name, area and routes, linked surfaces' text, and the question text including category descriptions. Recorded labels, status and file contents are never sent. The key is read only fromTYPESAFE_API_KEY, never written, printed or included in errors. The dashboard server makes no outbound requests.assessments.yamlis created only on the firstassess.[Unreleased], andpackage.jsonis unchanged until release.assess, which costs tokens.--assess=constructorand similar prototype-key values pass the boolean lookup. Fix withObject.hasOwn.isMappingand others).npm run smoke:jevis a manual live check that runs only when a key is set.Testing
npm run check: 178/178 tests (up from 60 on v0.2.0), and the demo validates with no warnings.model: jev-example). Its triage queue shows oneneeds-triageand onedisagreesitem.🤖 Generated with Claude Code