Library › Agents & Automation AI › Software developers

Write instructions for a GitHub issue triage bot

  • For Software developers
  • You practice Showing an example of what you want
  • Time about 5 minutes

About this exercise

You're writing the instructions for a bot that triages new GitHub issues on your open-source library. It must give each issue one label (bug, feature, question or docs), ask for the library version in a comment when a bug report doesn't include one, comment with a link to the original on a duplicate, and never close or assign issues. Output exactly 7 numbered plain-text lines: one action per issue in order, then DONE.

Common mistakes when you ask AI for this

  • Not showing the log format. Left alone, the AI writes a friendly report with headings instead of a checkable action log. Try: Show it literally: "Format every line like 1. ACTION: tool(args), then ASK_HUMAN: and DONE: lines. Plain text."
  • Not giving the labels. The AI makes up labels like "enhancement" or "i18n". Try: Say: "One label: bug, feature, question or docs."
  • No rule for thin reports or duplicates. The AI labels a bug without a version and leaves duplicates unlinked. Try: Add: "Bug with no version: comment asking for it. Duplicate: comment linking the original."
  • Letting it close or assign. The AI closes the duplicate and pings maintainers on everything. Try: Add: "Never close or assign."

What a strong prompt includes

  • Gives the labels
  • Asks for the version
  • Handles duplicates
  • Forbids closing or assigning
  • Shows the action-log format

Practice this now ↑

Related exercises