issue-tracking

SKILL.md

Issues describe what needs to be done and why. Keep them high-level unless the user provides specific details.

When possible, include verification steps or hints that tell the implementing agent how to prove the issue is resolved. This helps ensure work is actually verified before being marked complete.

Why include verification? Agents should never claim work is done without evidence. If the issue itself describes how to verify, the implementing agent can follow those steps and provide concrete proof (command output, test results, screenshots, etc.).

Project issue tracking system. Use when creating, reading, updating, listing, or closing issues. Triggers on "create an issue", "add a bug", "track a task", "list issues", "show bugs", "what's open", "close issue", or any issue/bug/task management request. Source: miketromba/issy.

View raw