Jev GitHub issue work type

Classify the work requested in a GitHub issue

Paste the issue request to distinguish restoring failed behavior, adding a feature and changing documentation. Review mixed work before assigning a workflow.

What work does this issue request?Live API
Try an example

Original input for the Bug fix outcome. Edit the evidence to send a new request.

Source: Background discussion on X

Source and example scope

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Classify the requested issue work.

Decision rules and labels
Bug fixFeatureDocumentationMixed workNeed evidence
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

The requested work matters more than the issue label.

An author can call an issue a bug while asking only for a guide. The excerpt’s requested change gives the handler a more useful signal than a title keyword or an unverified existing label.

Bug fix requires a stated expected behavior that fails. Feature describes a new capability. Mixed work preserves an issue that requests both implementation and explanatory changes, rather than silently losing one request.

This classification does not assign a particular agent, estimate effort or prove that a defect exists. Those steps require the repository, handler capabilities and verification evidence.

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for github issue work types.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Paste the issue request to distinguish restoring failed behavior, adding a feature and changing documentation.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Bug fix, Feature, Documentation, Mixed work, Need evidence. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Need evidence before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Broken CSV exportBug fix99.0%
New XML exportFeature100%
Clarify setup notesDocumentation100%
Fix plus explainMixed work100%
Bug named in a docs requestDocumentation100%
Missing issue bodyNeed evidence100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Sorting an issue intake queue by requested work
  • Reviewing ambiguous issue labels before assignment
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Estimating a fix without repository evidence
  • Automatically closing an issue classified as documentation
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about GitHub issue work type.

The rubric explains the decision; the application owns the next step.

Is a missing feature automatically a bug?

No. The example calls it Bug fix only when the issue states that an existing expected behavior fails. A newly requested capability belongs under Feature.

Does the label select a coding agent?

No. Work type is an intake signal. A handler selection needs the agent’s capability and permission information.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own GitHub issue work type input

Edit the evidence above or use the Playground to test another bounded question.