A Quality Gate on Every Issue

Every new issue gets restated in one shape, scored, and checked
for what a fixer would still need. Whoever filed it, however fast.

Install Free on GitHub

🎁 Beta users (first 100 installs) receive 150 clarified issues a month, free during beta testing

-- beta seats remaining!

What Happens to Every Issue

1
An issue is opened, by a person or by a pipeline.
2
Within a minute it is read against the same criteria as every other: the problem, expected versus actual, steps, versions, who is affected.
3
It is restated in one shape, short enough that a maintainer can read the restatement instead of the issue.
4
It gets a clarity score, so a triager can sort the queue by it.
5
If something is missing, it asks the questions that would get it, two or three at most, together. If nothing is, it asks nothing.

Three quarters of the issues it sees arrive clear enough to work on. Those get a restatement and no questions.

Two Kinds of Author, Two Replies

Filed by a person, at their own pace

  • One specific sentence on what makes the report usable. No gush.
  • The problem restated in their own words.
  • The one or two things a fixer will still need, if any.
  • One diagram, and only if the issue has a flow or a state worth drawing.

Filed in bulk, or by a script

  • Problem. Expected. Missing. Nothing around them.
  • No greeting, no praise, no emoji.
  • Nothing repeated, nothing decorated.
  • The same clarity score, so the whole batch can be sorted.

Which reply an author gets is decided per author, from how fast they are filing, never per repository. A script and a colleague can share one tracker.

Who Reads the Restatement

🛡️ Maintainers read it instead of the issue
🔍 Triagers see what is missing without opening the thread
💻 Developers start from expected versus actual, already separated
👥 Managers see which reporters need help, from the scores
🤖 Pipelines that file issues get one structure on every one
📊 Everyone gets the same shape, so issues can be compared

What It Is Not

✕
Not an interrogation. When an issue leaves out what a fixer needs, it asks the two or three questions that would get it, together, and stops there. Never a questionnaire, never a template to fill in.
✕
Not a repeater. Reply to it and it answers in a sentence. It never posts the same summary twice or draws the same diagram twice.
✕
Not in charge. Comment !whatproblem stop on any issue and it leaves that issue alone. Comment !whatproblem analyze to call it onto one it skipped.

Put a Gate on the Tracker

Install once. Every issue after that arrives restated.

Install Free on GitHub

🎁 Beta users (first 100 installs) receive 150 clarified issues a month, free during beta testing

-- beta seats remaining!