Every new issue
Every new issue arrives without a label, and half the bug reports don't say how to reproduce the problem.
How it goes now
New issue.Read it.Bug or question?Add a label.No steps to reproduce.Type the same request again.Post.Next issue.
Every issue, the same two minutes.
Tell Kitewell once
When an issue is opened in my repo, have a model label it bug, enhancement, question, or documentation, and if it's a bug without steps to reproduce, post our standard request for them.
That's the whole setup. Kitewell lays out every step for you to check, and nothing is saved until you apply it.
Then it runs on its own
Issue #1207Running on this computer
- Read the new issueA model reads the issue and answers from a fixed list: bug, enhancement, question, or documentation, and whether a bug report lacks steps to reproduce.Done
- Label itgh adds that label to the issue.Done
- Ask for steps to reproduceOnly for a bug report without them: posts your standard request, word for word.Done
What you get instead
Issue #1207
Labeled bug. Asked for steps to reproduce.
Issues
| # | Title | Label | Asked for steps |
|---|---|---|---|
| 1207 | Export button does nothing | bug | Yes |
| 1206 | Dark mode for reports | enhancement | No |
| 1205 | How do I change the time zone? | question | No |
| 1204 | Typo in the install guide | documentation | No |
Good to know
- Anyone who opens an issue writes its text, so a model reads it, not a coding agent: a model cannot run anything, and its answer must be one of your labels.
- The request for steps to reproduce is your own text, posted as written, never words the model chose.
- GitHub starts each run through Kitewell's relay, with no port open on your computer. Set the webhook to take only issues.opened, and have Kitewell check GitHub's signature.
What it needs
- An API model: Anthropic, OpenAI, Gemini, or a local server
- A Git repository and the gh command
- Kitewell Personal or Team, signed in to Dagu Cloud, for the GitHub webhook
More chores
- Every new pull requestEvery pull request waits for my first pass, and most of what I flag, a careful second reader would have caught.
- Every morningEvery morning I open each pull request just to work out which one could break something.
- Every weekday at 2:00Some mornings the tests on main are red, and my first hour goes to finding out why and fixing it.